GLSL stucks Java application

Hey there, I've recently created a few shaders - it is the first time I work with shaders in JOGL. When I use shaders in my JOGL application (I'm sitting on Eclipse btw) and run it - everything is OK - so shaders work fine. The problem starts when I, for instance, close the window by X button: the java application is stuck in processes, in other words it never terminates as usual. Therefore I have to go to task manager and kill this process forcefully - this is annoying and, in any case, does not work as intended. When I do not use shaders - everything is fine - closing by X button kills the process. I have already tried to use "Hello, World" VS and FS (to be sure that VS and FS are perfectly correct) and the result is the same - again and again the application is stuck.

Is this a well-known issue, or am I doing something wrong? For instance, I don't do glDetachShader, glDeleteShader and glDeleteProgram in the end of application, since there is no "shutdown" function on GLCanvas (why btw?). So, if it is strongly recommended to execute glDetachShader, glDeleteShader and glDeleteProgram functions before closing the application - tell me where it is better to execute them. However, until now, I suppose that it is not that necessary, that's why I'm not doing it and therefore I don't understand why such application stuck happens...

On Tuesday, March 01, 2011 00:40:19 Haroogan [via jogamp] wrote:
let me guess: AMD Windows Catalyst driver - not the latest ?
(don't remember the version though)

update driver to latest .. and you might be fine, this is known at JVM exit.

~Sven

Here you go, I think this is the last version, isn't it?

So any ideas guys? The problem is still here. Does anybody has the same issue?

please provide a minimal testcase (and file a bug if you have time). All i can say is that it works fine for us with latest drivers.

a useful info would be the thread dump when the problem occurred. you can generate thread dumps comfortably with VisualVM - its shipped with jdk by default.

best regards,
michael

I've had last year JOGL release, after I have installed a fresh one (2011-03-03) the problem has gone away, gratz on that :)