Closed Bug 417101 Opened 16 years ago Closed 16 years ago

Firefox crashes on first exit after an update or fresh install

Categories

(Toolkit :: Application Update, defect, P1)

x86
Windows XP
defect

Tracking

()

VERIFIED DUPLICATE of bug 417115
mozilla1.9beta3

People

(Reporter: cbook, Unassigned)

References

Details

(Keywords: crash)

Attachments

(1 file)

Reproduced multiple times on Windows XP with Updates from alpha2, alpha3, alpha4, beta1de etc.

Steps to reproduce:
-> Clean Profile
-> Update from Versions before Firefox 3 Beta 3 (like Beta 1) to Beta 3 via Check for Updates
-> Firefox restarts to apply the update
-> When you exit now Firefox after the Update is applied, Firefox crashes on exit

Note, this is a one time crash, a later session is okay

http://crash-stats.mozilla.com/report/index/669bb7ca-d9be-11dc-8f5e-001a4bd46e84
Flags: blocking-firefox3?
Ditto.  Totally confirming.  From Beta2 to Beta3.
I'm getting this ONLY on "complete" installs after I force fallback. This is on
Intel OS X 10.5:

Beta 2 to Beta 3: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; ko; rv:1.9b2)
Gecko/2007121014 Firefox/3.0b2 -> Mozilla/5.0 (Macintosh; U; Intel Mac OS X
10.5; ko; rv:1.9b3) Gecko/2008020511 Firefox/3.0b3

Beta 1 to Beta 3: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; fr; rv:1.9b1)
Gecko/2007110903 Firefox/3.0b1 -> Mozilla/5.0 (Macintosh; U; Intel Mac OS X
10.5; fr; rv:1.9b3) Gecko/2008020511 Firefox/3.0b3

This is done with new profiles. The crash doesn't happen every time but the
symptom on OS X is a Firefox hang on first complete shutdown/exit after the
update is finished and you have the Beta 3 firstrun, etc.
I tried five times with the beta 1 french updates and hung three times.

I tried four times with beta 2 korean and hung twice.
To be clear, this happens on the beta update channel, but didn't happen on the betatest or releasetest update channels?

What about the channel could cause a crash?
Flags: blocking-firefox3? → blocking-firefox3+
Priority: -- → P1
Target Milestone: --- → Firefox 3 beta3
We did not see this on releastest earlier.
(In reply to comment #4)
> To be clear, this happens on the beta update channel, but didn't happen on the
> betatest or releasetest update channels?
> 
> What about the channel could cause a crash?
> 

Yes, in my case the Windows XP release test updates were okay, the updates from
beta crash, also as example on a normal update from DE beta 1 to Beta 3 via
check for updates.
Are we positive the bits are the same in both channels?  Does this happen with full or partials?  Would be great to see those crash stacks..
I just went back and checked on releasetest with the same Korean build and I just got it. I'm wondering if somehow it is certain mirrors and not others?

Since I get a hang, I get no crash data. OS X just tells me that the app is not responding after I quit.
(In reply to comment #7)
> Are we positive the bits are the same in both channels?  Does this happen with
> full or partials?  Would be great to see those crash stacks..

Checking this now, but it looks the same to me. I'm wondering if it's a problem with one of our mirrors.
Flags: blocking-firefox3+ → blocking-firefox3?
Priority: P1 → --
Target Milestone: Firefox 3 beta3 → ---
Another crash stack is
http://crash-stats.mozilla.com/report/index/bd785402-d9c0-11dc-8abe-001a4bd43ef6?date=2008-02-12-23
btw.

Note: the Profile seems to be working after this crash. All bookmarks and
settings are still there and no data is lost.

also just to point this out, its a crash after exit, so it does not crash
during user operation.
We've got a much smaller user base for B3.  Can we pull all mirrors from bouncer and self-host as we debug?
Yes - we have 2x mirrors at ISC and a few in San Jose.  They can cover the load.  Just let us know when...
Attached file last update log
the update log from (in this last crash) crash from DE beta 1 -> beta 3 DE
(In reply to comment #9)
> (In reply to comment #7)
> > Are we positive the bits are the same in both channels?  Does this happen with
> > full or partials?  Would be great to see those crash stacks..
> 
> Checking this now, but it looks the same to me. I'm wondering if it's a problem
> with one of our mirrors.

Bits and channels look consistent. From the description, I can't think of a way this would be a mirror problem, though; sorry for the noise.
(In reply to comment #9)
> (In reply to comment #7)
> > Are we positive the bits are the same in both channels?  Does this happen with
> > full or partials?  Would be great to see those crash stacks..
> 
> Checking this now, but it looks the same to me. I'm wondering if it's a problem
> with one of our mirrors.
> 

ummm...if the shasums were invalid / corrupted, wouldn't the updater not accept the updates?
Ok, I forgot to attach a user agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3
also crash with the installer with no Firefox Profile before on Firefox 3 Beta3

->
http://crash-stats.mozilla.com/report/index/ea1365a8-d9c8-11dc-827a-001a4bd43e5c?date=2008-02-13-00

so this affects also the installer.
(In reply to comment #10)
> Another crash stack is
> http://crash-stats.mozilla.com/report/index/bd785402-d9c0-11dc-8abe-001a4bd43ef6?date=2008-02-12-23

Hey guys, since we have a stack overflow here, the web server can't report on it (the raw dump is too large...).  Here is the raw output from the dumps table in the db:
http://people.mozilla.com/~morgamic/bd785402-d9c0-11dc-8abe-001a4bd43ef6.rawdump.txt

Aravind is pulling the processed dump from 669bb7ca-d9be-11dc-8f5e-001a4bd46e84
and we'll have that in a few as well.
Updating summary.

We've now seen this bug in all instances, and can generalize it to being a crash upon exit after the first time the beta is run when doing:

 - fresh install
 - pave-over install
 - using binary installers
 - from updates
Flags: blocking-firefox3? → blocking-firefox3+
Priority: -- → P1
Summary: Firefox crash on exit after update to Beta 3 was applied → Firefox crashes on first exit after an update or fresh install
Target Milestone: --- → Firefox 3 beta3
This was caused by an animated favicon on the firstrun page.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Flags: blocking-firefox3+ → blocking-firefox3-
Verified dup
Status: RESOLVED → VERIFIED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.