A segfault is caused by accessing a memory address that is not allocated, so it looks like the garbage collector is trying to scan objects but is getting a dangling pointer to one that is already deallocated. Can you think of anything you’re doing in your game module that might cause this situation? Can you reproduce the error with an editor instance that is launched without your game module? Generally you would bisect this by removing half your game module and then trying to get the error, if not then add half back, if so remove another half, and so on until you can isolate the code that is causing this.