Can’t say much about that one - “Display not created” sounds like the display wasn’t created yet, but if he’s alt-tabbing to windows, presumably the game already started.
Is he running in windowed or in fullscreen mode? In windows mode, maybe somehow the window gets disposed, destroying the display. I guess that could trigger that “Display not create” exception as well.
Does jme3 have logging for Display creation and destruction? That would give you a hint what code paths might be killing the Display (or creating too late).
If there is no logging, bytecode enhancement can add log statements at class load time.
Executive summary is on http://stackoverflow.com/questions/8493056/java-byte-code-injection .
(Warning: I haven’t used that myself, I found it easier to explicitly add log statements )
He’s US timezone so I can’t get more feedback yet He said he was running in fullscreen mode and it happened when he alt tabbed out but other than that I don’t have many details so far.
Ok, I’ve just been talking with the tester in question. There has been another case where it has happened and while the previous ones have all been on an alt tab this one just happened in the middle of playing. At the time the game had been up and running for at least a couple of hours. I asked him to check the logs and there was another exception just before the one that we have seen before:
Jan 25, 2013 10:54:45 PM net.herodex.client.main.Main handleError
SEVERE: Unhandled error An OpenGL error has occured!
org.lwjgl.opengl.OpenGLException: Invalid framebuffer operation (1286)
at org.lwjgl.opengl.Util.checkGLError(Util.java:59)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.checkGLError(LwjglAbstractDisplay.java:136)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.runLoop(LwjglAbstractDisplay.java:157)
at com.jme3.system.lwjgl.LwjglDisplay.runLoop(LwjglDisplay.java:185)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:228)
at java.lang.Thread.run(Unknown Source)
Jan 25, 2013 10:54:46 PM net.herodex.client.main.Main handleError
SEVERE: Unhandled error Error while swapping buffers
java.lang.IllegalStateException: Display not created
at org.lwjgl.opengl.Display.update(Display.java:638)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.runLoop(LwjglAbstractDisplay.java:162)
at com.jme3.system.lwjgl.LwjglDisplay.runLoop(LwjglDisplay.java:185)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:228)
at java.lang.Thread.run(Unknown Source)
Jan 25, 2013 10:54:46 PM net.herodex.client.main.Main handleError
SEVERE: Unhandled error Uncaught exception thrown in Thread[LWJGL Renderer Thread,5,main]
java.lang.IllegalStateException: Display not created
at org.lwjgl.opengl.Display.processMessages(Display.java:595)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.runLoop(LwjglAbstractDisplay.java:181)
at com.jme3.system.lwjgl.LwjglDisplay.runLoop(LwjglDisplay.java:185)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:228)
at java.lang.Thread.run(Unknown Source)
Every other case has been when alt-tabbing, this is the first one while the game is running usually.
Every case has been on this same hardware, always when in full-screen mode.
The alt-tab crash is repeatable. Every time he tabs out it crashes. He’s going to try the jme demo later and see if he gets the same crash.
I asked him to turn shadows off and try and it fixed the crash. - Shadows off, tab 6 times no problems. Shadows Standard, crashed 3 times in a row.
@zarch said:
I'm sure it's not helping, but still I'd like to stop it crashing ;)
It’s fine on his main computer, crashes on his laptop…
Buy your beta tester a new laptop?
Seriously though, any possibility his video drivers are not up to date? Maybe a revert or downgrade could help. Since you’re having that problem from seemingly only 1 user, odds are it’s his setup and nothing is wrong with HeroDex.
)
