Closed
Bug 103968
Opened 24 years ago
Closed 24 years ago
Crash after downloading Java Runtime Enviroment Plug-in
Categories
(Core Graveyard :: Java: OJI, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mzagaja, Assigned: edburns)
Details
(Keywords: crash)
Attachments
(1 file)
|
464.28 KB,
image/png
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4+) Gecko/20011006
BuildID: 2001100610
After the JRE is downloaded the browser crashes, and causes talkback to send a
bug report. However the browser doesn't recognize JRE even though the computer
says it's installed in the control panel.
Reproducible: Always
Steps to Reproduce:
1. Download the JRE
2. Witness the crash
Actual Results: The browser crashes and no Java applets work
Expected Results: Mozilla should have had the JRE installed and working,
showing all Java applets.
Error Message:
Mozilla has caused an error in JS3250.DLL
Comment 2•24 years ago
|
||
-> OJI
-> Critical
Reporter: When you get a Talkback-caught error such as in your screenshot,
please complete that process, then post the Talkback ID here.
Severity: blocker → critical
Component: Browser-General → OJI
Keywords: crash
Whiteboard: crash, stackwanted
Okay 2 things:
1. Where would I find the talkback ID? I looked for it and couldn't find it.
2. I now am using build #200110903 and it no longer crashes. However the JRE
plug-in still won't work :-(.
Comment 6•24 years ago
|
||
Matthew:
1. You can find the Talkback ID by running talkback.exe, found here:
<mozilla dir>/bin/components/talkback.exe
2. As you no longer have the crash, I'm marking this bug WORKSFORME. Please file
a separate bug for your Java issue. First, though, I would recommend that you
follow the instructions in the release notes:
http://www.mozilla.org/releases/mozilla0.9.4/#java
3. "OJI" is the Mozilla component for tracking bugs dealing with Sun's Java plugin.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Whiteboard: crash, stackwanted
I no longer have a problem after following instructions on page!
You need to log in
before you can comment on or make changes to this bug.
Description
•