Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350002 - Browser crash when run BrowserFunction with SWT 32bit component on Win7(64bit) system.
Summary: Browser crash when run BrowserFunction with SWT 32bit component on Win7(64bit...
Status: CLOSED DUPLICATE of bug 343932
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-22 02:32 EDT by guoyun CLA
Modified: 2011-06-22 09:55 EDT (History)
1 user (show)

See Also:


Attachments
Sample java code (3.82 KB, application/octet-stream)
2011-06-22 02:35 EDT, guoyun CLA
no flags Details
Java core dump file (68.30 KB, text/plain)
2011-06-22 02:36 EDT, guoyun CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description guoyun CLA 2011-06-22 02:32:21 EDT
Build Identifier: 3.6.2 GM build

Browser crash when run BrowserFunction with SWT 32bit component on Win7(64bit) system.

Reproducible: Always

Steps to Reproduce:
1. Download the SWT 362 GM(swt-3.6.2-win32-win32-x86.zip) from server.
2. Run the attached sample(which is a simple js-java application) with above SWT binary.
3. Click the "Puch to Invoke Java" button in browser, the application crashed with dump.
Comment 1 guoyun CLA 2011-06-22 02:35:25 EDT
Created attachment 198368 [details]
Sample java code
Comment 2 guoyun CLA 2011-06-22 02:36:02 EDT
Created attachment 198369 [details]
Java core dump file
Comment 3 guoyun CLA 2011-06-22 02:41:03 EDT
The sample code run well on Win7(32bit) system, but always crashed on Win7(64bit). And from the java core dump file, we can see the crash occurred at WebSite.convertToJS() method: arrayTypeDispatch.QueryInterface (COM.IIDIDispatchEx, result) line.
Comment 4 Grant Gayed CLA 2011-06-22 09:55:27 EDT
This is fixed in 3.7.

*** This bug has been marked as a duplicate of bug 343932 ***