Closed Bug 297513 Opened 20 years ago Closed 20 years ago

random closing of firefox 1.04 build

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: shinigami_shungotenshi_2003, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)

i could open a link in a new tab and it will close firefox.  when i reopen
firefox and try to go to the same site and it will close again. i have xp
service pack 2 which is kept updated all the time

Reproducible: Sometimes
Please retry it with a nightly developer build (Deer Park) because the Gecko in
FF1.0.4 is over 12+ months old.
And please also post a Talkback ID from such a crash in a trunk build that you
started in the Firefox safemode.

marking invalid (out-of-date build and without steps to reproduce or Talkback ID)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
i allow firefox to update. this is what the about says "Mozilla/5.0 (Windows; U;
Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4" so it can't be
that. it normally happens when i go to mail.yahoo.com, or 4chan.org. those are
the main sites that it does the closing of the browser
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
You are using the latest Firefox Release Version (Firefox1.0.4) but this Release
is based on a 12+ months old Gecko. 
(Gecko is a part of Mozilla, Firefox, Thunderbird and it's the component that
does the rendering, Networking etc.)

The Gecko 12+ months old because Firefox1.0.4 is basically Firefox1.0 plus
additional security fixes but nothing more.
Too old means that bug reports doesn't help developing Gecko and bugzilla is
only a place for the developers to track their work and it's not for support.
(You can use the mozillazine.org Forums for support questions)

Again,there are a few problems with your bug report:
a) FF1.0.4 is too old (it doesn't matter that it's the latest release).
b) We need a talkback ID from those crashes because tehy are random
c) You have to crash Firefox in the Firefo safemode to be sure that no extension 
is causing the crashes.

That means: We need Talkback Crash IDs from a current developer nightly build
running in the safemode or with a new Profile.

marking invalid again

Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.