Home » Eclipse Projects » Standard Widget Toolkit (SWT) » XulRunner errors on Windows(XulRunner crashes eclipse somewhat randomly on windows xp)
XulRunner errors on Windows [message #553499] |
Tue, 17 August 2010 17:12 |
Michael Bowman Messages: 1 Registered: July 2009 |
Junior Member |
|
|
Ok, I'm at my wits end on this one and am hoping that someone here can help me with this. I have a few SWT Browser views in my client application. One of them uses JavaScript and the JSBridge pretty heavily to pass messages back and forth to the java side.
I have xul runner in a folder at <app_root>/plugins/com.foo.client_2.1.0/resources/xulrunner
and in my activator before a browser view is created, I get the location of that folder using the FileLocator.resolve() method and set the system property org.eclipse.swt.browser.XULRunnerPath with the location of xulrunner.
Everything starts up fine and runs fine for a long time, but then the entire app crashes with:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x78147748, pid=3896, tid=672
#
# JRE version: 6.0_14-b08
# Java VM: Java HotSpot(TM) Client VM (14.0-b16 mixed mode windows-x86 )
# Problematic frame:
# C [MOZCRT19.dll+0x17748]
#
# 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.
#
[...]
Stack: [0x001d0000,0x002d0000], sp=0x002cdc54, free space=1015k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [MOZCRT19.dll+0x17748]
C [xul.dll+0x64c27a]
j org.eclipse.swt.internal.mozilla.XPCOM._VtblCall(III[C)I+0
j org.eclipse.swt.internal.mozilla.XPCOM.VtblCall(III[C)I+11
j org.eclipse.swt.internal.mozilla.nsIWritableVariant.SetAsWSt ringWithSize(I[C)I+12
j org.eclipse.swt.browser.External.convertToJS(Ljava/lang/Obje ct;Lorg/eclipse/swt/internal/mozilla/nsIComponentManager;)Lo rg/eclipse/swt/internal/mozilla/nsIVariant;+111
j org.eclipse.swt.browser.External.convertToJS(Ljava/lang/Obje ct;Lorg/eclipse/swt/internal/mozilla/nsIComponentManager;)Lo rg/eclipse/swt/internal/mozilla/nsIVariant;+267
j org.eclipse.swt.browser.External.convertToJS(Ljava/lang/Obje ct;Lorg/eclipse/swt/internal/mozilla/nsIComponentManager;)Lo rg/eclipse/swt/internal/mozilla/nsIVariant;+267
j org.eclipse.swt.browser.External.callJava(III)I+230
j org.eclipse.swt.browser.External$4.method3([I)I+13
J org.eclipse.swt.internal.mozilla.XPCOMObject.callback3([I)I
v ~StubRoutines::call_stub
V [jvm.dll+0xecabc]
V [jvm.dll+0x173d61]
V [jvm.dll+0xecb3d]
V [jvm.dll+0xf5705]
V [jvm.dll+0xfc38d]
C [swt-win32-3557.dll+0x145f]
C 0x45fd0a98
C [xul.dll+0x641fc9]
C [xul.dll+0x26479]
I can get it to happen fairly quickly by repeatedly opening and closing a view with a browser in it.
Any suggestions or clues as to where else I can look to solve this?
Thanks,
-Michael
|
|
|
Re: XulRunner errors on Windows [message #553718 is a reply to message #553499] |
Wed, 18 August 2010 14:48 |
Grant Gayed Messages: 2150 Registered: July 2009 |
Senior Member |
|
|
Hi Michael,
This looks like a bug in swt or possibly xulrunner. I would first suggest
trying your case with eclipse/swt 3.6 if this is not what you're already
using. If this does not help then please log a report with swt at
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform &component=SWT
and provide some means of reproducing the crash, and be sure to specify
which xulrunner version you're using. If you CC me on the report then I
will look into it when I have a chance.
Grant
"Michael Bowman" <michael@scrumchum.com> wrote in message
news:i4efut$lo7$1@build.eclipse.org...
> Ok, I'm at my wits end on this one and am hoping that someone here can
> help me with this. I have a few SWT Browser views in my client
> application. One of them uses JavaScript and the JSBridge pretty heavily
> to pass messages back and forth to the java side.
>
> I have xul runner in a folder at
> <app_root>/plugins/com.foo.client_2.1.0/resources/xulrunner
> and in my activator before a browser view is created, I get the location
> of that folder using the FileLocator.resolve() method and set the system
> property org.eclipse.swt.browser.XULRunnerPath with the location of
> xulrunner.
>
> Everything starts up fine and runs fine for a long time, but then the
> entire app crashes with:
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x78147748, pid=3896,
> tid=672
> #
> # JRE version: 6.0_14-b08
> # Java VM: Java HotSpot(TM) Client VM (14.0-b16 mixed mode windows-x86 )
> # Problematic frame:
> # C [MOZCRT19.dll+0x17748]
> #
> # 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.
> #
>
> [...]
> Stack: [0x001d0000,0x002d0000], sp=0x002cdc54, free space=1015k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> C [MOZCRT19.dll+0x17748]
> C [xul.dll+0x64c27a]
> j org.eclipse.swt.internal.mozilla.XPCOM._VtblCall(III[C)I+0
> j org.eclipse.swt.internal.mozilla.XPCOM.VtblCall(III[C)I+11
> j org.eclipse.swt.internal.mozilla.nsIWritableVariant.SetAsWSt
> ringWithSize(I[C)I+12
> j org.eclipse.swt.browser.External.convertToJS(Ljava/lang/Obje
> ct;Lorg/eclipse/swt/internal/mozilla/nsIComponentManager;)Lo
> rg/eclipse/swt/internal/mozilla/nsIVariant;+111
> j org.eclipse.swt.browser.External.convertToJS(Ljava/lang/Obje
> ct;Lorg/eclipse/swt/internal/mozilla/nsIComponentManager;)Lo
> rg/eclipse/swt/internal/mozilla/nsIVariant;+267
> j org.eclipse.swt.browser.External.convertToJS(Ljava/lang/Obje
> ct;Lorg/eclipse/swt/internal/mozilla/nsIComponentManager;)Lo
> rg/eclipse/swt/internal/mozilla/nsIVariant;+267
> j org.eclipse.swt.browser.External.callJava(III)I+230
> j org.eclipse.swt.browser.External$4.method3([I)I+13
> J org.eclipse.swt.internal.mozilla.XPCOMObject.callback3([I)I
> v ~StubRoutines::call_stub
> V [jvm.dll+0xecabc]
> V [jvm.dll+0x173d61]
> V [jvm.dll+0xecb3d]
> V [jvm.dll+0xf5705]
> V [jvm.dll+0xfc38d]
> C [swt-win32-3557.dll+0x145f]
> C 0x45fd0a98
> C [xul.dll+0x641fc9]
> C [xul.dll+0x26479]
>
> I can get it to happen fairly quickly by repeatedly opening and closing a
> view with a browser in it.
>
> Any suggestions or clues as to where else I can look to solve this?
>
> Thanks,
> -Michael
>
|
|
| |
Re: XulRunner errors on Windows [message #628955 is a reply to message #628935] |
Fri, 24 September 2010 21:17 |
W. Adams Messages: 2 Registered: September 2010 |
Junior Member |
|
|
I have also done some additional testing in Eclipse 3.5 (but unfortunately on a 64-bit Windows XP box), and by setting the Eclipse preference for Web Browser to EXTERNAL, rather than internal, I got a slightly different indication of 'Problematic frame':
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x01e96d21, pid=496, tid=3900
#
# JRE version: 6.0_21-b06
# Java VM: Java HotSpot(TM) Client VM (17.0-b16 mixed mode windows-x86 )
# Problematic frame:
# J org.eclipse.swt.internal.mozilla.XPCOM._JS_EvaluateUCScriptF orPrincipals([BIII[CI[BI[I)I
#
# 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.
#
(If this seems like it might be any more helpful in deciphering the root cause of this crash, I can send a more complete copy of the log.)
Thanks again for your help!
W. Adams
[Updated on: Mon, 27 September 2010 16:50] Report message to a moderator
|
|
| | | |
Goto Forum:
Current Time: Fri Apr 19 10:03:43 GMT 2024
Powered by FUDForum. Page generated in 0.02212 seconds
|