Bug 712 - Using GLCanvas and the SWT_AWT bridge reveals a JavaEmbeddedFrame when ran with Java 7
Summary: Using GLCanvas and the SWT_AWT bridge reveals a JavaEmbeddedFrame when ran wi...
Status: UNCONFIRMED
Alias: None
Product: Jogl
Classification: JogAmp
Component: awt (show other bugs)
Version: 3.0.0
Hardware: All linux
: --- major
Assignee: Petros Koutsolampros
URL:
Depends on:
Blocks: 674
  Show dependency tree / graph
 
Reported: 2013-04-03 15:29 CEST by Bart Adams
Modified: 2023-07-12 01:29 CEST (History)
2 users (show)

See Also:
Type: DEFECT
SCM Refs:
Workaround: ---

Attachments
Sample code (needs JOGL and swt.jar) that illustrates the GLCanvas bug when ran on linux with java 7 (1.40 KB, text/x-java)
2013-04-03 15:29 CEST, Bart Adams 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bart Adams 2013-04-03 15:29:23 CEST 
Created attachment 449 [details]
Sample code (needs JOGL and swt.jar) that illustrates the GLCanvas bug when ran on linux with java 7

We experience several issues with GLCanvas when used with the SWT_AWT bridge from swt.jar and ran using Java 7 under linux.

When attached sample is started with Java 7, it does not behave as expected (showing a single frame with a GLCanvas in it). Instead, most of the time it shows two frames of which one is called JavaEmbeddedFrame. On dual screen setups it can also end up in an infinite loop where the embedded frame is destroyed and created over and over.

The issue does not occur with Java 6.

The issue also does not occur when using a regular Canvas. This suggests that the bug is introduced in GLCanvas.java.