Closed
Bug 99285
Opened 24 years ago
Closed 24 years ago
browser lock up
Categories
(Core Graveyard :: Java: OJI, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: spigel, Assigned: joe.chou)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010801
BuildID: 2001080104
if (page contain java applet) then {
browser and other mozilla's application lock( my window manager show one
title bar for each mozilla's window.
I use Mozilla 0.9.3 and (jdk1.3.1 or jre1.3.1) from Sun.
Output on my console:
java_vm file not found
^^^^^^^^^^^^
Why? Realy, i not have java_vm, but jdk1.3.1 | jre1.3.1 contain only vm named:
"java".
Reproducible: Always
Steps to Reproduce:
if not hove jdk1.3.1 or jre1.3.1 please download it from sun.com. install it.
copy plugins from jdk1.3.1/jre/plugins/i386/ns600/libjavaplugin_oji.so to
mozilla plugins directory.
run mozilla -0.9.3.
1. switch to browser and type in the address bar
<path_to_installed_jdk1.3.1>/demos/applets/<select_any_applets>/example1.htm[l]
or type ixbt.com
2. You see lock up.
3. To close window please kill all mozilla-bin threads
Actual Results: browser and other mozilla's application lock up
I use Mozilla- 0.9.3, jdk-1.3.1,
XFree86 4.1.0, twm | kde | WindowMaker | icewm | balckbox
and CPU := i686( Intel Celeron), Memory := 128M, Video := Ati 3D Rage IIC,
MotherBoard := developing with Via Appolo Pro chipsets.
Comment 1•24 years ago
|
||
Are you using RH7.1 ?
Comment 2•24 years ago
|
||
> copy plugins from jdk1.3.1/jre/plugins/i386/ns600/libjavaplugin_oji.so
This statement is WRONG. You should make a *symlink* to this file, not copy it.
Make it a symlinks and if it works then please mark this as INVALID.
Comment 3•24 years ago
|
||
Marking these all WORKSFORME sorry about lack of response but were very
overloaded here. Only reopen the bug if you can reproduce with the following steps:
1) Download the latest nightly (or 0.9.6 which should be out RSN)
2) Create a new profile
3) test the bug again
If it still occurs go ahead and reopen the bug. Again sorry about no response
were quite overloaded here and understaffed.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 4•24 years ago
|
||
no response from reporter after suggesting fix. should leave WFM.
| Reporter | ||
Comment 5•24 years ago
|
||
Sorry, i will today test now with mozilla 0.9.5 and
new java vm from sun.com (1.4.1 beta3).
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
| Reporter | ||
Comment 6•24 years ago
|
||
I install java 1.4.0 beta3 build 84 in /usr/local/java-home/jre.
export JAVAHOME=/usr/local/java-home/jre
export PATH=$PATH:/usr/local/java-home/jre/bin
my mozilla located in my HOMEDIR: $HOME/mozilla
[]$ cd $HOME/mozilla/plugins
[]$ ln -s /usr/local/java-home/jre/lib/plugin/i386/ns610/libjavaplugin_oji140.so
[]$ mozilla
If in mozilla settings java is enable then mozilla segmentation fault without
create core dump.
if java not enable then mozilla succesfull start, but about:plugins show
incorrect information about java plugin.
This correct(equal) for ns600 plugins.
| Reporter | ||
Comment 7•24 years ago
|
||
With ns4 java plugin mozilla work fine!
why not work with ns6xx series?
I test with java 1.4.0 beta3 b84
mozilla 0.9.5
and Mandrake 8.1
Comment 9•24 years ago
|
||
Marking nEW based on reporters comments.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 10•24 years ago
|
||
reassigning to default component assignee.
Assignee: asa → joe.chou
QA Contact: doronr → pmac
| Reporter | ||
Comment 11•24 years ago
|
||
All test work with Mozilla 0.9.7!
bug not reproducible
I will change resolution to FIXED or remove this bug from bug list.
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Comment 12•24 years ago
|
||
This should be resolved WORKSFORME, not FIXED.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 13•24 years ago
|
||
Doing so.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•