From: Kenneth B. R. <kbr...@al...> - 2002-10-15 21:43:36
|
> I don't know if it's the same problem but I'm also having problems with > GL4Java-based apps when creating and destroying OpenGL components. After > a random number of create/destroy operations application hangs without > any error and has to be killed from task manager. This happens after > init() is called and before first display() call. I was just preparing > to track the problem down to specific line of code :-) > > I'm using JDK 1.4 with GNU/Linux. > > If someone needs any help in fixing this problem please let me know. Please do try to narrow down the root cause if you have time. The major change in GL4Java between JDK 1.3.1 and 1.4 is the use of the JAWT for acquiring the native window handle. If the code which uses JAWT doesn't handle all of the error cases properly then that is probably the source of the problems. |
From: Kenneth B. R. <kbr...@al...> - 2002-10-16 15:26:48
|
> I'm not sure if this is correct for the official binaries, but the > version of GL4Java that I compile from the cvs uses jawt in both the 1.3 > and 1.4 library. So I'm assuming this can't be causing the problem. Just checked the code in GLContext.java and you're right, for the Sun JDK 1.3 and above JAWT will be used. The IBM JDK will use an older fallback mechanism. Which are you using? Regardless, a substantial portion of the core GUI system was rewritten in the Sun JDK 1.4, so I can believe that the JAWT may now be returning result codes (like JAWT_LOCK_SURFACE_CHANGED) that it was not returning before. |
From: Pepijn V. E. <pep...@lu...> - 2002-10-17 08:10:12
|
On any pointers to some decent documentation on this stuff? I have no experience at all with the win32 api or jawt, so any tips before I start bug hunting would be very welcome :) Pepijn Van Eeckhoudt Kenneth B. Russell wrote: >>I'm not sure if this is correct for the official binaries, but the >>version of GL4Java that I compile from the cvs uses jawt in both the 1.3 >>and 1.4 library. So I'm assuming this can't be causing the problem. > > > Just checked the code in GLContext.java and you're right, for the > Sun JDK 1.3 and above JAWT will be used. The IBM JDK will use an > older fallback mechanism. Which are you using? > > Regardless, a substantial portion of the core GUI system was > rewritten in the Sun JDK 1.4, so I can believe that the JAWT may > now be returning result codes (like JAWT_LOCK_SURFACE_CHANGED) > that it was not returning before. > |
From: Kenneth B. R. <kbr...@al...> - 2002-10-17 14:42:16
|
> On any pointers to some decent documentation on this stuff? I have no > experience at all with the win32 api or jawt, so any tips before I start > bug hunting would be very welcome :) http://java.sun.com/j2se/1.4.1/docs/guide/awt/1.3/AWT_Native_Interface.html The JAWT documentation doesn't provide a lot of detail on the semantics. All I would recommend at first is instrumenting the GL4Java code with printf's to see the return values from the JAWT routines, in particular locking the drawing surface. See if the return value changes just before the crash on 1.4.1 and if it remains the same on 1.3.1. Documentation on SetPixelFormat and other Windows APIs can be found at http://msdn.microsoft.com/ . |
From: Pepijn V. E. <pep...@lu...> - 2002-10-16 08:02:21
|
I'm not sure if this is correct for the official binaries, but the version of GL4Java that I compile from the cvs uses jawt in both the 1.3 and 1.4 library. So I'm assuming this can't be causing the problem. Pepijn Van Eeckhoudt Kenneth B. Russell wrote: >>I don't know if it's the same problem but I'm also having problems with >>GL4Java-based apps when creating and destroying OpenGL components. After >>a random number of create/destroy operations application hangs without >>any error and has to be killed from task manager. This happens after >>init() is called and before first display() call. I was just preparing >>to track the problem down to specific line of code :-) >> >>I'm using JDK 1.4 with GNU/Linux. >> >>If someone needs any help in fixing this problem please let me know. > > > Please do try to narrow down the root cause if you have time. The > major change in GL4Java between JDK 1.3.1 and 1.4 is the use of > the JAWT for acquiring the native window handle. If the code > which uses JAWT doesn't handle all of the error cases properly > then that is probably the source of the problems. > > > ------------------------------------------------------- > This sf.net email is sponsored by: viaVerio will pay you up to > $1,000 for every account that you consolidate with us. > http://ad.doubleclick.net/clk;4749864;7604308;v? > http://www.viaverio.com/consolidator/osdn.cfm > _______________________________________________ > gl4java-usergroup mailing list > gl4...@li... > https://lists.sourceforge.net/lists/listinfo/gl4java-usergroup > |