AWTGLCanvas does not work with JDK 1.7

Started by Kai, September 30, 2009, 13:24:35

Previous topic - Next topic

Kai

Hi,

I have noticed a strange bug? with JDK 1.7 Build 72:
The swapBuffer does not seem to update the Canvas anymore...

All GL commands will be executed without any errors/warnings/etc. but I just do not get to see what I drew.
Even if I just make a glClear with a color, it won't work!

I tried the current JKD 1.6 build, and everything works fine, there.

Did anyone experience this, too?

lainmaster

Any reason not to use Display.setParent ?

Kai

QuoteAny reason not to use Display.setParent ?
Yes. I need multiple windows (we are using it in a CAVE environment) (4 windows per render node).

Matzon

I am not using JDK 7 at all - does the issue occur in 71? is it fixed in 73?

Kai

Quotedoes the issue occur in 71? is it fixed in 73?
Interestingly, it does not occur in b71, but sadly it does occur in b73!

Matzon

Quote from: Kai on October 03, 2009, 08:03:57
Quotedoes the issue occur in 71? is it fixed in 73?
Interestingly, it does not occur in b71, but sadly it does occur in b73!
so b72 introduced an "issue"?
http://download.java.net/jdk7/changes/jdk7-b72.html doesnt list anything particularly interresting ...

Fool Running

The change for "Javaw process taking up 80-90 percent of CPU time!" looks kinda suspicious to me:
http://hg.openjdk.java.net/jdk7/jdk7/jdk/rev/559fb14d0ae9
But I'm really not sure if that could cause your problems or not.
Programmers will, one day, rule the world... and the world won't notice until its too late.Just testing the marquee option ;D

Kai

Thanks at @ for you replies.

I circumvented this issue by switching back to Java 1.6.
The reason for using Java 1.7 in the first place was the need to load multi-channel (5.1 channels) wave files, as there is a nice class "WaveExtensibleFileReader" that allows this.

Now, I found another way to load these wave files and can go back to 1.6, and after all, it sounds a little strange to move to another java version just because of a new class :-), but still, this bug is annoying...