This GPF may appear if SLLs that have been saved with the image are unbound.
SLLs contain several segments which are loaded into memory.
One if these segments is the so called metaspace, which is only needed temporarily.
So after alle SLLs have been bound, the memory allocated for metaspace is being freed, but internal structures still contain the pointer to the formerly allocated memory address.
It now may happen that this same memory address is being allocated by the JIT compiler during image startup.
If the SLL that formerly used the memory block is being unbound, all memory is being freed so the memory block for metaspace is being freed again. Because this memory block is now used by the JIT compiler this causes a GPF as soon as the JIT compiler is being activated.