Since this problem is actually reproducible on your system, it would help more if you could help to debug it so that it can actually be fixed. I'd really appreciate a thread state dump at the point where the screen is white. Producing such information is not
entirely trivial, however, so it depends on your computer prowess. Here's the basic procedure:
Download the requisite Jar files to a directory; the necessary ones are:
Then, you need to unpack JOGL's DLL files to somewhere the dynlinker can find them -- I'm not sure just how Windows does that, but I
think you can just put them in the same directory as the Jar files. The DLL files are inside a pair of other Jar files, but Jar files are just ordinary Zip files, so you should be able to extract them with any Zip program (though on Windows, I imagine that you may need to rename the Jar files to have the .zip extension to be able to open them). On ordinary 32-bit Windows, the Jar files you need to extract DLL files from are the following:
After that, open a command prompt (I assume that you're a Windows user), go to the directory into which you put the Jar and DLL files, and run the following command:
- Code: Select all
java -jar haven.jar sh.seatribe.se
The client should then run normally. Then, when the screen has gone white, focus the command prompt window and press Control+Backslash. Upon doing so, Java should produce the thread state dump. Please post it here.