Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
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 Go to next message
Michael Bowman is currently offline Michael BowmanFriend
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 Go to previous messageGo to next message
Grant Gayed is currently offline Grant GayedFriend
Messages: 2151
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 (now with Eclipse PDE 3.6) [message #628935 is a reply to message #553499] Fri, 24 September 2010 19:22 Go to previous messageGo to next message
C. Shamis is currently offline C. ShamisFriend
Messages: 1
Registered: July 2009
Junior Member
Hi Grant,

I'm taking this effort over for Michael. We took your advice and moved our application to Eclipse PDE 3.6, but we're unable to get a build out... It's complaining about singleton versions selected in the pde-build section. I'm not seeing this when I build against 3.5.2.

I'm tracking this down on several other forums at the same time, but is anybody else seeing this type of error in their 3.6 builds?

     [java] 
     [java] generateFeature:
     [java] [eclipse.generateFeature] Some inter-plug-in dependencies have not been satisfied.
     [java] [eclipse.generateFeature] Bundle org.eclipse.pde.build:
     [java] [eclipse.generateFeature] 	Another singleton version selected: org.eclipse.pde.build_3.6.0.v20100603
     [java] [eclipse.generateFeature] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
     [java] [eclipse.generateFeature] 	Another singleton version selected: org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
     [java] 


Thanks,
-C.
Re: XulRunner errors on Windows [message #628955 is a reply to message #628935] Fri, 24 September 2010 21:17 Go to previous messageGo to next message
W. Adams is currently offline W. AdamsFriend
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

Re: XulRunner errors on Windows (now with Eclipse PDE 3.6) [message #629219 is a reply to message #628955] Mon, 27 September 2010 13:34 Go to previous messageGo to next message
Grant Gayed is currently offline Grant GayedFriend
Messages: 2151
Registered: July 2009
Senior Member
Based on what you've pasted I think you're seeing
https://bugs.eclipse.org/bugs/show_bug.cgi?id=288710 , which was fixed in
eclipse/swt >= 3.5.2.

Grant


<wendy.adams@gd-ais.com> wrote in message
news:i7j4bb$g20$1@news.eclipse.org...
>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, and 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
Re: XulRunner errors on Windows (now with Eclipse PDE 3.6) [message #630927 is a reply to message #629219] Tue, 05 October 2010 15:23 Go to previous messageGo to next message
W. Adams is currently offline W. AdamsFriend
Messages: 2
Registered: September 2010
Junior Member
Your suggestion did get my failure to match Michael's, but I am still having trouble figuring out what kinds of things to look for that could be 'bad' or 'risky' in the way we are handling interaction between the Java and Javascript. I've been asked to build a 'small' test workspace to see if we can reproduce it in a simpler setup, but I'm not sure what minimum set of stuff would even be necessary, much less representative. Can you point me to a tutorial or snippet that might be ideal for this? Thx!
Re: XulRunner errors on Windows (now with Eclipse PDE 3.6) [message #631433 is a reply to message #630927] Thu, 07 October 2010 14:24 Go to previous message
Grant Gayed is currently offline Grant GayedFriend
Messages: 2151
Registered: July 2009
Senior Member
Some minimal snippets that call between Java and JS are:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org. eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet307 .java
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org. eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet308 .java

Hopefully one of these provides a good basis for implementing a case that
reproduces the crash you're seeing.

You may wish to start by adding some logging to your crashing app, to record
every JS<->Java interaction you're about to make, to see if there are
certain argument(s) being passed that are causing the problem. Note string
arguments in particular since the crash is happening in
nsIWritableVariant.SetAsWStringWithSize(...).

Grant


"W. Adams" <wendy.adams@gd-ais.com> wrote in message
news:i8ffn4$gcu$1@news.eclipse.org...
> Your suggestion did get my failure to match Michael's, but I am still
> having trouble figuring out what kinds of things to look for that could be
> 'bad' or 'risky' in the way we are handling interaction between the Java
> and Javascript. I've been asked to build a 'small' test workspace to see
> if we can reproduce it in a simpler setup, but I'm not sure what minimum
> set of stuff would even be necessary, much less representative. Can you
> point me to a tutorial or snippet that might be ideal for this? Thx!
Previous Topic:Re: Data getting truncated in a TableViewer
Next Topic:Close context menu when mouse is not hovering it
Goto Forum:
  


Current Time: Sat Nov 22 13:30:49 GMT 2014

Powered by FUDForum. Page generated in 0.11969 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software