Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344381 - [SWT_AWT] VM crash when disposing a native control on UI with multiple controls
Summary: [SWT_AWT] VM crash when disposing a native control on UI with multiple controls
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.0   Edit
Hardware: PC Mac OS X
: P3 critical with 7 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-30 13:57 EDT by Christopher Deckers CLA
Modified: 2013-08-19 06:43 EDT (History)
1 user (show)

See Also:

Attachments
Tesrt case showing the crash (2.94 KB, application/octet-stream)
2011-04-30 14:01 EDT, Christopher Deckers 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 Christopher Deckers CLA 2011-04-30 13:57:53 EDT 
Build Identifier: SWT 3.7M7

When more than one native control is present on the UI, disposing them crashes the VM. The native controls I am using are Browser widgets with default runtime (Safari).

Result in console: Invalid memory access of location 0x20 eip=0x98843ed7

VM options: -XstartOnFirstThread -d32


Reproducible: Always

Steps to Reproduce:
See attached test case.
Comment 1 Christopher Deckers CLA 2011-04-30 14:01:04 EDT 
Created attachment 194427 [details]
Tesrt case showing the crash

There is a constant that allows to test with other number of component. With 1, a component can be added/disposed/added/etc without any issues.
Comment 2 Lakshmi P Shanmugam CLA 2013-07-22 06:46:02 EDT 
I tried this with 4.3 build and do not see any crash. The snippet works fine, though a NPE is printed in the console.
Can you pls. try this with the 4.3 build and see if it crashes?
Comment 3 Lakshmi P Shanmugam CLA 2013-08-19 06:43:23 EDT 
Closing report as it is not reproducible with 4.3. Please reopen if you can reproduce the crash.