Closed
Bug 206608
Opened 22 years ago
Closed 22 years ago
java plug-in crashes the 1.4 beta browswer
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: Gary.Beckmann, Assigned: peterlubczynski-bugs)
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030507
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030507
We have the following java installed:
> java -version
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)
Anything that requires java, including the java console window will crash the
browser. This does not occur using 1.4 alpha.
Reproducible: Always
Steps to Reproduce:
1.Click Tools/Web Development->Java Console
2.
3.
Actual Results:
Browser crahses, error message in shell window:
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 rules:0.0.
INTERNAL ERROR on Browser End: Could not read ack from browser
System error?:: Resource temporarily unavailable
Expected Results:
The Java console should appear -- as it does in 1.4 alpha.
The version of mozilla with which the java plug-in works is:
Mozilla 1.4a, Copyright (c) 2003 mozilla.org, build 2003040105
Reporter | ||
Comment 1•22 years ago
|
||
Just found out why the java plug-in wasn't working. I went to remove it from
the plugins directory and noticed that it wasn't a symbolic link-- probably when
the beta was installed the plugins were copied (and I'm probably the one who did
it). By Changing to a symbolic link to
/usr/java/j2re1.4.1_02/plugin/i386/ns610/libjavaplugin_oji.so
the crash no longer occurs.
Still a crash (with no talkback invoke?!?) is a brutal way to handle a mistake
in installing plugins.
Comment 2•22 years ago
|
||
>Still a crash (with no talkback invoke?!?) is a brutal way to handle a mistake
>in installing plugins.
Ask Sun why the plugin calls simple "exit()" which Mozilla can't survive because
it runs in the same process.
A copied plugin never worked on Linux because the Plugin can't find the JVM
without symlinking
-> invalid
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•