135369 - URL crashes mozilla (due to applet?)

Status: RESOLVED WORKSFORME

(Core Graveyard :: Java: OJI, defect)

Description

[Matt Fago]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020403
BuildID:    2002040308

Loading the given applet crashes Mozilla without warning or Talkback.

Reproducible: Always
Steps to Reproduce:
1.Load URL
2.
3.

Actual Results:  Crash

Expected Results:  Load URL

This is probably a duplicate of one of the many applet / javascript bugs already
filed ... but I'm not sure which one.

Comment 1

[Matt Fago]

This also happens on:

http://java.sun.com

Konquorer correctly renders page, but several applets are greyed out with the
message "Java applet is not loaded (jave interpreter disabled)"

By the way, the applet mentioned in the origional report only seems to print
"Hello World."

Comment 2

[Matthias Versen [:Matti]]

Reporter:
Which JRE type do you use ?
Have you symlinked the plugin (and not copied) to the mozilla plugin folder ?

-> Oji (=Java / Java!=Javascript)

Comment 3

[Matt Fago]

The JRE is 1.3.1_01. I'm downloading 1.4 right now (slowly).

No, I did not symlink the plugin. Where is it supposed to be installed, and why
the symlink?

Comment 4

[Matthias Versen [:Matti]]

I'm a win32 user :-)
but from the release notes:
http://www.mozilla.org/releases/mozilla0.9.9/#java :

"Make a soft link from /plugins/libjavaplugin_oji.so to
/usr/java/j*/jre/plugins/i386/ns610/libjavaplugin_oji.so "

You can get a crash if you copy the plugin..

Comment 5

[Matt Fago]

Ok, the symlink does fix the bug. RTFM ;-)

Why the crash though? Will this issue eventually be addressed, and if so what is
the existing bug?


JRE 1.4.0 works fine too BTW.

Comment 6

[Joe Chou]

Tried it on Solaris, and it worked too. Mark it WORKSFORME.
Xiaobin, do you know the answer to Matt's question: why would it crash if the
Java plugin lib was copied to plugins directory instead of making a symbolic
link?

Comment 7

[Xiaobin Lu]

No idea! Matt, do you have the stack trace?

Comment 8

[Matt Fago]

So there is no plan to ever fix this bug? The easy work around should rule it
out for 1.0 and even maybe 1.1, but it _is_ a crasher, no?


Here is what comes up on the command-line:

INTERNAL ERROR on Browser End: Exec of "java_vm" failed: 2
<
System error?:: No such file or directory


How to I obtain a stack trace? 

Talkback does not activate in this case, and I cannot seem to get mozilla
running in a debugger (with mozilla -g): it gives me the error "init.c not found."

Comment 9

[Matthias Versen [:Matti]]

The java plugin can't find the JVM if you copy the plugin and you get a crash.
(You get also crash if you change mozilla's UA String and the JVM rejects to
load with the wrong UA)

Comment 10

[Matt Fago]

It still seems that Mozilla should be able to handle the plugins better so that
an errant java (or flash!) plugin cannot bomb the entire application.

I've had both crashed happen regularly. This one is easy to work around, but the
flash issue is only resolved by removing the (poorly written) plugin.

Hopefully this particular bug with java will no longer be an issue for anyone
when the automatic java plugin installer actually works.

Comment 11

[Igor Nekrestyanov]

Yep, plugin uses actual library location to deduce location of jvm executables.
The problem is widely known and documented in release notes.

As for mozilla's unability to survive this - this is also well known problem 
and caused by java plugin design ("around success" paradigm).
Current plugin implementations simply call exit() if any serious error happens.
Because exit() is called on the mozilla side (in the same process) - we can not
survice this :(

This was already discussed in several bugs here. 
For instance see bug 105287.

Comment 12

[Phil Schwartau]

*** Bug 142995 has been marked as a duplicate of this bug. ***