mac and linux testers req.

[krigun]

Tested on the MacBook as described in my earlier post, and still getting the same behaviour. Sorry. Can't really see whats wrong either, since there is no evidence of an exception. The app just stops responding.

[ryanm]

Yep, same behaviour as before. Could you make an executable jar version so we can check for deadlocks?

[arielm]

Great Idea! Here's a self-executable jar file:

http://www.chronotext.org/lab/DEBUG1.jar (363K)

I added some System.out progress messages that should be helpful to isolate the issue.

The jar's manifest is as follows:
Class-Path: jogl.zip gluegen-rt.jar
Main-Class: debug3.Tokyo_15_DEBUG1

Therefore, on my system, I put the jar in a directory together with:
- jogl.zip
- gluegen-rt.jar
- jogl.dll
- jogl_awt.dll
- gluegen-rt.dll

In order to see the output, I launch with something like:
java -classpath DEBUG1.jar debug3.Tokyo_15_DEBUG1 >output.txt

Supposing everything runs without bugs, the output looks like:
Tokyo_15.init(): BEGIN...
Tokyo_15.init(): TEXTURE LOADED
Tokyo_15.init(): FONT CREATION BEGIN...END
Tokyo_15.init(): BACKGROUND LOADED
Tokyo_15.init(): END
Tokyo_15.display(): FRAME 1
ZFont.allocate: BEGIN...END
ZFont.initTexture: ENTITY '83' BEGIN...END
...
ZFont.initTexture: ENTITY '80' BEGIN...END
Tokyo_15.display(): FRAME 2

Thanks!

Games published by our own members! Check 'em out!

[Ken Russell]

FYI, you should be able to use the jstack program that ships with the JDK to get a thread dump from an arbitrary deadlocked process containing the JVM. You just need to figure out the process ID. There is a jps command which should help with this as well.

[ryanm]

Sorry for the delay, find attached the stack trace. I couldn't see anything obvious, but that's maybe just me

[arielm]

thank you bleb, definitely helpful!