Bug 300246 - SWT_AWT bridge and a Transparent Composite cause 100% cpu
Summary: SWT_AWT bridge and a Transparent Composite cause 100% cpu
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-20 14:05 EST by James CLA
Modified: 2019-09-06 16:17 EDT (History)
1 user (show)

See Also:

Attachments
Repro case. (1.36 KB, application/zip)
2010-01-20 14:05 EST, James CLA 		no flags 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 James CLA 2010-01-20 14:05:02 EST 
Created attachment 156693 [details]
Repro case.

In our application, I've determined that using the SWT_AWT bridge to display an AWT control, and also set the SWT.Transparent flag on an SWT Composite, leads to 100% cpu under Windows XP.   It seems the AWT control may be constantly painting.  It only occurs in this configuration.

I've attached some code to repro the issue.

Please run SWT_AWT_BridgeTest on a Windows XP system (bare metal), using SWT 3.5.0.  This bug does not occur on Vista, or when running XP in a virtual environment under Vista.

Please let me know if you have any questions.  Thanks.  James
Comment 1 Remy Suen CLA 2010-01-20 14:23:24 EST 
Sounds kind of like bug 297588.
Comment 2 James CLA 2010-01-21 14:58:41 EST 
(In reply to comment #1)
> Sounds kind of like bug 297588.

Possibly, but the solution in bug 297588 was to use Control#setRegion() instead of using the SWT.TRANSPARENT flag.

In our case, we're doing something different.  We want to have a gradient background in the parent composite to show through the transparent children composites.  Currently this works well, unless we use the SWT_AWT bridge to display an AWT control.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:17:37 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.