Hi folks!
I'm in **Month 32** of a solo project, and a lockup-inducing bug has been cropping up intermittently for about six months now. I thought I'd have found it by now, but the game is nearly complete and I'm no closer to identifying the cause.
The lockups aren't that difficult to duplicate, but I can't pin down precise conditions. I have discovered that they only occur after the game has been left paused for a while, OR after the application has switched out of focus for a while. But I can't always trigger the problem on purpose.
There's so much logic that might be responsible (even given these isolated criteria), I really cannot fathom how to approach finding the cause(s).
The first error reported is always that my "supervisor" singleton instance is nullified. Because so many classes call this expecting it to be non-null, knowing this doesn't tell me anything about why it's happening.
All subsequent errors seem related to this one, but in the same frame, it stops producing new errors and locks up, requiring me to terminate the process.
I'm very confident that there's no logic that should be capable of nullifying this instance, so I'm really at a loss for what's happening. I don't even know what to try first to find out. I'm also not sure it has anything to do with the root of the problem. In fact it seems more likely it's only a primary symptom.
**Any advice?** Really any at all might help. I'm unfamiliar with debugging "complete unknowns" in a complex project.
↧