Bugzilla – Full Text Bug Listing
| Summary: | JVM and IE8 crash | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Odif Xeth <thexred> | ||||||||
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | beckmann.manuel, daniel_megert, marcins, orgler | ||||||||
| Version: | 3.7.1 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows 7 | ||||||||||
| Whiteboard: | stalebug | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Odif Xeth
We have this problem as well: our Eclipse-3.7.2 based RCP-Application is failing from time to time. We have this problem especially when running the app (that shows an IE-Window) on win server 2008 R2 SP1 with IE9 that runs as a terminal server. It is reproducible there in 2 of 3 runs I guess. Any ideas on howto narrow this further down? This is what the error dialog shows: Problemsignatur: Problemereignisname: BEX Anwendungsname: horus.exe Anwendungsversion: 0.0.0.0 Anwendungszeitstempel: 4d87abff Fehlermodulname: jscript9.dll Fehlermodulversion: 9.0.8112.16440 Fehlermodulzeitstempel: 4eb31a04 Ausnahmeoffset: 00001a7f Ausnahmecode: c0000005 Ausnahmedaten: 00000008 Betriebsystemversion: 6.1.7601.2.1.0.18.10 Gebietsschema-ID: 1031 Zusatzinformation 1: 0a9e Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789 Zusatzinformation 3: 0a9e Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789 We've attempted to investigate this as a potential IE bug, but the lack of repro steps prevented us from making much progress. If someones comes up with a repro, I'd like to look at this again. Martin Sawicki Principal Program Manager Microsoft Open Technologies, Inc. A subsidiary of Microsoft Corporation Dear Martin, thanks for your interest in this. Unfortunately we couldn't reproduce this on a second machine. (Initially since we only have one windows server 2008 R2 Terminal server. But on this machine it is absolutely reproducible. The problem occurs on appx. 8 out of 10 starts of our product. I could propose the following steps: 1. you could simply test our RCP-App on a win2008-r2-terminal-server (german one if this is interesting, with latest SP on the server). The JDK is bundled with the app. You can download the app (freeware) at http://www.horus.biz/en/horus-iinsidei/performance-range/horus-endeavor/download.html 2. if you cannot reproduce this on your machine with the given app, we can of cause start some type of desktop-sharing-session where I could show you the issue. If necessary I could of cause also provide more details on the machine/OS; just tell me what you need. Regards, Johannes Created attachment 214782 [details]
Locally stored test file for IE9 SWT browser crash.
1) Edit the iframe URL in this file to reflect the location of where you store the remote test file (CrashTestRemoteFile.html).
2) Load this file locally from an IE9 SWT browser instance, eg. file:///c|/Test/CrashTestLocalFile.html
3) Close the browser, which should then produce a fatal exception.
Created attachment 214783 [details]
Remote file for IE9 SWT browser crash test.
Store this file remotely, anywhere as long as it's not on the same server as the local file.
Explanation of the above two attachments: Here is a test case that for me always produces a fatal exception on an IE9 SWT browser instance. The basic gist of it is that the Javascript execution of window.top.location from an embedded iframe - from a different URL than the parent - produces a permission denied error, as it normally would, but this also seems to send the embedded IE9 browser into an unstable state. Once that particular browser instance is closed, the entire Java app bombs out with an exception in jscript9.dll. I'm also aware of cases where the app will produce the fatal error as soon as the page is loaded. For this test case I've been using the bare bones SWT browser snippet outlined at http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet128.java . Environment: Windows 7 64-bit, IE9.0.8112.16421 Java: Both Sun JDK 1.6.0_25 64-bit and 1.7.0_01 32-bit SWT: 3.7.2 32 and 64-bit, 3.7.1 32 and 64-bit, 3.6.1 32-bit Please let me know if more info is needed. Hopefully this can help track down the issue. Regards, Russ Created attachment 214850 [details]
WinDbg call stack
For the Microsoft folks investigating the problem, here's WinDbg's stack trace at the time of the crash, using the most recent test case above.
Using JDK 1.6.0_25 64-bit and SWT 3.7.2 64-bit for this run, but the stack trace always seems to be the same regardless, including for other web pages which also cause the browser to crash.
Hope this helps, please let me know if you'd like any more info from my end.
Regards,
Russ
Russ, thanks for the extra info, very valuable, but this now tells me what you're seeing is bug 354640, not this one. Still looking at Johannes' repro, since that callstack looks a bit different. 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |