Ok, very odd issue.
Starts off simple enough: basically, one of the developers here had made a mistake, and bound some drawing code to some keyboard input instead of changing an object being drawn. Now since input happens on a different thread, JOGL should totally crash (given that the change of state could happen between a begin and end.
Here is the issue tho: it worked. When run from the command line on actual computers no errors were thrown. In fact, the only time it would actually crash is when the application was launched via webstart. It would crash hard, taking down the poor client’s VM.
My hope would be that an error such as that would crash all the time, not just via webstart. Any ideas on why it would act in a such a way?