167778 - Talkback fails to activate on INTERNAL ERROR Exec of "java_vm" failed: 2

Status: RESOLVED INVALID

(Core Graveyard :: Java: OJI, defect)

Description

[Bryce Mozilla Nesbitt]

Talkback fails to activate when faced with this situation:


I visit http://bioengineering.org/ and get on the console

INTERNAL ERROR on Browser End: Exec of "java_vm" failed: 2
<System error?:: No such file or directory
Gdk-ERROR **: Fatal IO error 9 (Bad file descriptor) on X server :0.0.
INTERNAL ERROR on Browser End: Could not read ack from browser
System error?:: Resource temporarily unavailable

The browser window simply disappears.


See http://bugzilla.mozilla.org/show_bug.cgi?id=162682

Comment 1

[David Bradley]

This was my fear, that we may have a lot of incidents where the VM decides
things are very bad and rather than crashing just terminates the process. This
is what I was seeing when running Purify. This might be due to the way Mozilla
is starting up the process, or might be an issue inside the JVM. Unfortunately
there's no easy way to know. We'll need help from Sun to know what could cause
the JVM to decide to terminate the process. If we know what conditions this
would occur under, we might be able to figure out if Mozilla is causing it or not.

Comment 2

[Stephen Ostermiller]

I get this same error with j2sdk1.4.0_01 and all builds for the last several
months, including the latest nightly: 2002120605
It happens any time I visit any page with a Java plugin.

INTERNAL ERROR on Browser End: Exec of "java_vm" failed: 2
<
System error?:: No such file or directory
Gdk-ERROR **: Fatal IO error 9 (Bad file descriptor) on X server :0.0.
INTERNAL ERROR on Browser End: Could not read ack from browser
System error?:: Resource temporarily unavailable

Any word on what causes this probem

Comment 3

[Shiva Thirumazhusai]

-> mcafee

Comment 4

[timeless]

jvm doesn't trigger a crash, it just tells the client to forcibly quit mozilla.
there's nothing Talkback can do, and it's unlikely OJI can do much.

*if* jvm provides its stack info, it /might/ be possible for the mozilla side to
generate a report containing the oji info, but the mozilla stack to oji wouldn't
be useful since the problem isn't there.

Comment 5

[Joshua Xia]

I can't reproduce this bug. I guess your java plugin is not installed correctly.
Please create symbloic link to jre/plugin/i386/ns610/libjavaplugin_oji.so in
mozilla's plugins directory, don't copy the phyiscal file in it!

Please confirm it and will close this bug.

Comment 6

[Joshua Xia]

->close