I did a quick search on the forums for problems with JOGL and JVM crashes, and found a lot of questions related to the subject. I'm about to start investigating our own Jogl / AWT related JVM crash and I was hoping that I could get some advice on where to start.

The crash frequency is directly related to input on AWT. So far it has only happened during mouse movement on screen. It is indirectly related to the amount of rendering we are doing in our engine -- the more rendering we are doing on screen the greater the frequency of the crashes that occur.

We are using immediate mode for just about everything at the moment -- we are drawing textured quads, text, and lines to the screen. I've updated to the latest JDK (1.6 update 21), and I've made sure that I have the correct jogl dlls (Amd x64).

Specs:AMD Athalon II x4 630 ProcessorATI Radeon HD 5700 Series

The beginning of the crash log:--------------- T H R E A D ---------------

We finally 'resolved' this issue. It turns out that switching to a 32-bit JVM and i586 dlls fixed all of our problems. I went in with an opengl debugger and could find absolutely nothing out of the ordinary with our opengl states at the time of the crashes. Should I be filing a bug somewhere?

JOGL 1.1.1a is no more maintained, you have to switch to JOGL 2 that adresses the problem of multiple displays for example. If you reproduce your bug with JOGL 2, then I will advise you to write a bug report.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org