Closed Bug 274779 Opened 20 years ago Closed 20 years ago

firefox suddenly exits

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: enightingale, Assigned: bugzilla)

References

()

Details

(Keywords: crash)

Viewing this page with the latest nightly build of Firefox causes the program
to immediately exit.  Occurs with the 1.0 build, not with the 1.0 pre-release.
Does not occur with the latest Mozilla nightly build.

Thanks

Ed Nightingale
Seems to be non-deterministic.  I reproduced the bug several times in a row,
then it occured only intermittently.
The page uses Java.

Disable Java in TOOLS - OPTIONS - WEB FEATURES
If the crash disappears, the problem lies with your Java engine.

In that case, see http://plugindoc.mozdev.org/ how to get your Java brewing
properly.

Can you report your findings back here?

Lowering severity to CRITICAL [click on SEVERITY above]
Blocker  	Blocks development and/or testing work
Critical 	crashes, loss of data, severe memory leak
Adding crash keyword.

In case your problem is NOT java related can you post a talkback id?
Severity: blocker → critical
Keywords: crash
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a6) Gecko/20041213
Firefox/1.0+

(Debug build from my own tree, a few days old)

Java Plug-in

    File name: Java Applet.plugin
    Java 1.3.1 Plug-in

WFM
Looks like java is the culprit.  Thanks for your help.  If this is in Java
is there a way to manage it so that Firefox issues an error and simply refuses 
to render the page, or is Java stack stomping and wiping everything out?
I guess I could fire up gdb but maybe I'll just get a newer Java engine :)

Thanks again

Ed Nightingale
(In reply to comment #4)
> Looks like java is the culprit.  Thanks for your help.  If this is in Java
> is there a way to manage it so that Firefox issues an error and simply refuses 
> to render the page, or is Java stack stomping and wiping everything out?
> I guess I could fire up gdb but maybe I'll just get a newer Java engine :)

marking wfm.
There are some bugs open asking for to tolerate plugin malfuction or something
in those words, but as far as i know there's no real solution for this as of now...
I'm sorry, for now the solution seems to be to upgrade your Java.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.