Closed Bug 77306 Opened 24 years ago Closed 24 years ago

Java crashes the browser

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 76373

People

(Reporter: exe, Assigned: edburns)

References

()

Details

(Keywords: crash)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.3-20mdk i686; en-US; 0.8.1) Gecko/20010420 BuildID: 2001042010 Bad: The java plugin crases mozilla 0.8.1. I have tried both jdk1.3.0_01 and jdk1.3.0_02 but both crash on this page. Reproducible: Always Steps to Reproduce: 1.go to the webpage http://www.library.uiuc.edu 2.Wait for the applet to initialize 3. Actual Results: Mozilla crashed Expected Results: Displayed the page properly with the java applet running
moving to oji
Assignee: idk → edburns
Reporter do you have the stacktrace from the crash?
Keywords: crash
MOZILLA caused an invalid page fault in module JVM.DLL at 017f:50437960. Registers: EAX=02e5d7a4 CS=017f EIP=50437960 EFLGS=00010246 EBX=02e5d7a4 SS=0187 ESP=0068c59c EBP=0068c5e4 ECX=00000000 DS=0187 ESI=0068c5b8 FS=4eef EDX=0068c60c ES=0187 EDI=00000000 GS=0000 Bytes at CS:EIP: 8b 01 56 57 8b 79 04 8b 70 38 6a 0c e8 53 b1 fe Stack dump: 50441199 02e5d750 50444359 00000000 0068c60c 02e5d7a4 00000000 00000037 02e5d750 0068c600 5045ed70 00000037 02e5d750 02e5d7a4 0000000e 00000000
Well, whats the follow up on this bug. It crashes my mozilla. I posted the error message. I think this should be marked as a bug that needs fixing asap.
Confirming with Linux build 2001042515. Before the crash, the system was rather unresponsive, as if the Java VM was sucking up CPU time, but I didn't start top in time to see if this was actually true. Moving to OJI. As far as I can tell, it's the java_vm process that crashes, as it leaves behind a core file; mozilla-bin doesn't leave any core file for this crash, so I guess that it's exiting through exit(). The last thing that mozilla outputs before the crash is: # HotSpot Virtual Machine Error, Unexpected Signal 11 # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Error ID: 4F533F4C494E55580E43505005BC # # Problematic Thread: prio=1 tid=0x842ccd0 nid=0x518 runnable # INTERNAL ERROR on Browser End: Pipe closed during read? State may be corrupt System error?:: Success
Status: UNCONFIRMED → NEW
Component: Java-Implemented Plugins → OJI
Ever confirmed: true
Yeah my system froze when it tried to load the java too. But when I hit close on the error box my broswer shut down like it would in any other error. I finally got java to work in mozilla its just that in order to run java now it has to open the java consol in order to do it.
I'll try this when I get a good build.
Reproduced the problem with mozilla08.1, and got the following error on Java console which is identical of bug 76363. Making this one duplicate of 76363. Error on Java console: ... PLUGIN ERROR ************ Java process: unexpected request ffffffff *** This bug has been marked as a duplicate of 76363 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Also tried it on April 30's trunk build. This time, instead of crash, got a class not found error on Java console: load: class NavBar.class not found.
Took a look at the page, in the applet of NavBar class, try to use absolute path instead of relative ("/NavBar"), and the class not found problem may go away.
I meant in the HTML page's applet tag for NavBar class, in codebase field, instead of using relative path, give it the whole path.
Wrong dup specified.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
*** This bug has been marked as a duplicate of 76373 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → DUPLICATE
Changing QA contact
QA Contact: geetha.vaidyanaathan → avm
Oops, this bug should be a duplicate of 76373, not 76363. Reopen and then redo duplicate.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
This bug should be a duplicate of 76373, which has the same error message on Java console. *** This bug has been marked as a duplicate of 76373 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.