Posted by Alexis Drogoul on Apr 21, 2015; 12:10pm
URL: https://forum.jogamp.org/Hangs-and-Freezes-JOGL-2-2-4-2-3-0-MacOS-X-Yosemite-JDK-6-7-8-SWT-3-8-2-4-4-2-tp4034199p4034355.html

Hi,

Yes, I figured out the various changes in JOGL2 compared to JOGL1. The problem is that the same code (nothing fancy, just creating a texture from an image, binding it to the current GL context, and displaying it) works flawlessly in JOGL 2.2.4, but does not display anything in JOGL 2.3.1. Any hint where it might come from ? I've tried to understand the changes between the two versions, but it's a bit complex to figure out.

Of course, it's perfectly possible that another part of our rendering system is the indirect cause of this malfunction, so I'll dig a bit more the changes introduced in JOGL 2.3.1.

Regarding the problems of memory, I guess it comes from a bad management of textures, but I still have to find the cause as well (the same code was working without these problems in JOGL1). Actually, we create and destroy a lot of textures (maybe a little bit too much, but that's another problem we will have to deal with later !) during the run of a simulation, and it seems that in some cases they are not properly destroyed…

Thanks anyway for your previous feedbacks — I'll come back to this forum if I make some progress — or not :) !

Cheers
Alexis