Tested on 1.10 locally.

Compiling and running an opaque closure eventually calls registerJITObject

This maps the JIT address to the methodinstance globally in the JIT:

Later on, this will be looked up, e.g., but lookupLInfo for stacktraces.

However, it appears that the OpaqueClosure's MI is not globally rooted. Which means that it gets garbage collected. But garbage collection does not remove things from the jit registration. And thus when the stack trace mechanism tries to find it.....it segfaults

cc @vchuravy @Keno @vtjnash @gbaraldi