We have a client who runs our program that uses an SWT Browser component.
We have some pages where unpredictabally, about every 10. time, the JVM crashes with a fatal error. These pages seemingly only differ from other pages in that they use a javascript function created in SWT. To make matters worse, we cannot reproduce it in our development environment, but at our client it occurs on more than one computer.

We have the fatal error log (see attachment). I never debugged such a log before, could someone help me and give me a hint on what the log says, what can we try?

I can take a guess, though without more context that's all it is. The
top-listed native frame is JVM_FindSignal, so the crash actually looks
like it's happening in the JRE (it's not just being trapped there). I
also notice in the loaded libraries list that there are Java libraries
loaded from both C:\Woodpecker\WoodpeckerVIR\Java\... and
C:\PROGRA~1\Java\jre6\... , which is generally not a good thing to do.
The C:\PROGRA~1\Java\jre6\... libraries are being loaded by the
"-Xbootclasspath/a:..." JVM startup arg, which I assume is there in
order to make applets work. The JRE at C:\Woodpecker\WoodpeckerVIR\Java
is presumably being used to launch your app (?).

So the first thing to try is to get rid of the "-Xbootclasspath/a:..."
JVM startup arg and see if it makes the crashes go away. If it does
then the fix is likely to just ensure that the JRE at
C:\PROGRA~1\Java\jre6\... is used to launch your app, since this MUST be
the same JRE that is used by native browsers to render applets AND be
pointed at by "-Xbootclasspath/a:...". If it does not help then look at
the new error log and at least confirm that Java libraries only being
loaded from C:\PROGRA~1\Java\jre6\... and nowhere else.

HTH,
Grant

On 11/6/2012 3:06 AM, János Gerevich wrote:
> We have a client who runs our program that uses an SWT Browser component.
> We have some pages where unpredictabally, about every 10. time, the JVM crashes with a fatal error. These pages seemingly only differ from other pages in that they use a javascript function created in SWT. To make matters worse, we cannot reproduce it in our development environment, but at our client it occurs on more than one computer.
>
> We have the fatal error log (see attachment). I never debugged such a log before, could someone help me and give me a hint on what the log says, what can we try?
>
> Thank you,
> John
>

Re-reading my response, the "get rid of '-Xbootclasspath/a:...' part
misses the point by a bit. Just skip this and ensure that your app is
being launched with the JRE at C:\PROGRA~1\Java\jre6\..., so that the
the JRE at C:\Woodpecker\WoodpeckerVIR\Java\... is not involved in any way.

Grant

On 11/15/2012 11:16 AM, Grant Gayed wrote:
> Hi John,
>
> I can take a guess, though without more context that's all it is. The
> top-listed native frame is JVM_FindSignal, so the crash actually looks
> like it's happening in the JRE (it's not just being trapped there). I
> also notice in the loaded libraries list that there are Java libraries
> loaded from both C:\Woodpecker\WoodpeckerVIR\Java\... and
> C:\PROGRA~1\Java\jre6\... , which is generally not a good thing to do.
> The C:\PROGRA~1\Java\jre6\... libraries are being loaded by the
> "-Xbootclasspath/a:..." JVM startup arg, which I assume is there in
> order to make applets work. The JRE at C:\Woodpecker\WoodpeckerVIR\Java
> is presumably being used to launch your app (?).
>
> So the first thing to try is to get rid of the "-Xbootclasspath/a:..."
> JVM startup arg and see if it makes the crashes go away. If it does
> then the fix is likely to just ensure that the JRE at
> C:\PROGRA~1\Java\jre6\... is used to launch your app, since this MUST be
> the same JRE that is used by native browsers to render applets AND be
> pointed at by "-Xbootclasspath/a:...". If it does not help then look at
> the new error log and at least confirm that Java libraries only being
> loaded from C:\PROGRA~1\Java\jre6\... and nowhere else.
>
> HTH,
> Grant
>
>
> On 11/6/2012 3:06 AM, János Gerevich wrote:
>> We have a client who runs our program that uses an SWT Browser component.
>> We have some pages where unpredictabally, about every 10. time, the
>> JVM crashes with a fatal error. These pages seemingly only differ from
>> other pages in that they use a javascript function created in SWT. To
>> make matters worse, we cannot reproduce it in our development
>> environment, but at our client it occurs on more than one computer.
>>
>> We have the fatal error log (see attachment). I never debugged such a
>> log before, could someone help me and give me a hint on what the log
>> says, what can we try?
>>
>> Thank you,
>> John
>>
>