A player reports to me that one of my games dies after starting up, leaving an unresponsive black screen.
After giving him a version with extra logging, I determined that the problem occurs when the game calls setFullScreenWindow() in the (default) GraphicsDevice. It never returns from that call. Of course, it could be that he is getting impatient and killing the process before setFullScreenWindow() can generate an exception or even return without throwing an exception.
Now, it’s possible that this player has driver problems, etc. But how to debug this particular failure? Would turning on the assertions in the JVM provide more information? I didn’t try changing the trace level, yet, either. I plan to prepare a hotfix for him which would generate some additional information. I am just not sure how best to do that. I suppose that in the long run the best approach might be to compile a custom JVM? Well, I don’t have the knowledge to do that. Not this week, anyway.