Community
Participate
Working Groups
Build Identifier: M20100211-1343 I'm developing a plugin for eclipse that relies on the SWT Xulrunner browser for windows xp. To test the plugin i've been using the PDT and running a copy of eclipse from within eclipse. The browser will load a page, but after scrolling or doing some stuff with jquery it crashes with the following error: # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0510cdc2, pid=2376, tid=3000 # # JRE version: 6.0_18-b07 # Java VM: Java HotSpot(TM) Client VM (16.0-b13 mixed mode, sharing windows-x86 ) # Problematic frame: # C [xul.dll+0x4bcdc2] # # An error report file with more information is saved as: # H:\eclipse\hs_err_pid2376.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # I've tried using different xulrunners including 1.9.2 and 1.8.0.9 through starting the eclipse copy using -Dorg.eclipse.swt.browser.XULRunnerPath , but they all seem to give the same error. Xulrunner 1.9.3a5 seems to work, but the <canvas> element no longer works which is needed by my project. Reproducible: Always
Created attachment 169751 [details] error log Error Log from eclipse
http://github.com/pj/beat thats the source of my project
Oops... sorry, it appears to be working now, I think this was caused by the Windows XP firewall blocking XPCOM. Sorry for the trouble.
Okay, I was wrong it's still broken with the same problem
> after scrolling or doing some stuff with jquery it crashes The error logs look like the Browser is being disposed. I assume you meant that the crash happens at dispose time, after scrolling/doing stuff? Is it possible to provide just a page (along with its accompanying jquery libs, etc.) that can be navigated to in Eclipse's Internal Web Browser view to show the problem? Having a small case would make investigating this much easier. Also, can you verify that it still happens in a recent eclipse 3.6 build like http://download.eclipse.org/eclipse/downloads/drops/I20100608-0911/index.php?
Support for Mozilla style browser has been dropped for 4.8. See Bug 518446