JOGL Animator class locks up my computer

OpenGL Development JOGL Development
#1

The JOGL Animator class really screwed up on my computer… Let me try to explain…
The symtoms:
My project runs fine on 4 other Windows machines and 1 Linux machine I’ve tried. However, on my Windows machine, it freezes and locks up my whole computer for about 5-10 seconds every time I put my mouse over the window or touch a key. This leads me to believe that there is something wrong with the window receiving events. It must have something to do with the Animator class because this does not happen if I disable the Animator class in my code.
I am using window code from the NeHe tutorials. The problem occurs in all of the Nehe tutorials I’ve tried. It also used to occur in the official JOGL demos but after removing all traces of Java from my system and reinstalling JDK 1.4.2_07 the JOGL demos work fine. My code and the NeHe code still does not, however.

I have tried compiling on another machine and running it on mine, and it still does not work. This leads me to believe there is something wrong with my JVM, but I can’t imagine what. Weird how reinstalling the JVM fixed the official JOGL demos but not my stuff…

My C++ OpenGL demos work fine, so I doubt it has anything to do with drivers/OpenGL.

I do not believe this to be a hardware issue but I will post my specs to assure you:
AMD AthlonXP Barton 2500+
1024MB DDR 333 RAM
WindowsXP SP2

I am using the exact same JOGL version as the other Windows machines (copied the dll/jar over directly). I’ve also tried the newest beta release on the release server (though I haven’t tried CVS).

Any guesses? Perhaps someone can point me to instructions on how to completely remove all traces of Java from my machines? (So far all I’ve done is use the uninstaller and then delete the leftover directories).

Thanks for your help!
-Kevin Wood

#2

What graphics card are you using?

ATI graphics cards in particular have, at least until now, extremely poor driver quality for multithreaded OpenGL applications. We have fixed a few bugs in JOGL’s single-threaded workaround for ATI cards recently and at this point with the code in the CVS repository everything is running rock solid on ATI cards. We’ve been able to close most of the open JOGL bugs with the latest round of fixes.

If you’re running on an ATI card, then in the forthcoming 1.1 b08 things will magically get better. Until then you can run with 1.1 b07 and specify -DATI_WORKAROUND=true on the command line. (This system property was changed to JOGL_SINGLE_THREADED_WORKAROUND in 1.1 b08, and is enabled earlier in the startup process, fixing a few remaining problems).

#3

Aye, a Radeon. I had meant to mention that, must have been distracted.
Thank you very much for your helpful reply. I will check out the CVS code.
Out of curiosity, was this information posted anywhere? I spent quite a lot of time looking for answers to this by myself before I posted, and turned up nothing. ATI cards are pretty common, I’m suprised I didn’t see this posted somewhere.

I’ll come back to update the thread when I’ve tried the CVS code.

Thanks again!
-Kevin Wood

#4

We’re somewhat lacking in documentation of recent changes like the single-threaded workaround. Check out the JOGL Release Information thread for information about some recent changes. However, 1.1 b08 should fix all such problems, at least on Windows, so hopefully this kind of problem should never show up again… ;D

#5

1.1b07 fixed the problem. I was sure I’d tried it, but I guess I must have put it in the wrong VM or something. Thanks a lot for the help.