82630 - Crash occurs if browser left open after updating to new release

Status: VERIFIED DUPLICATE of bug 85307

(Core Graveyard :: Installer: XPInstall Engine, defect)

Description

[Jimmy Lee]

Build: 2001-05-24-09-trunk(WIN), 2001-05-24-08-trunk(MAC), 
2001-05-23-08-trunk(LINUX)

1. Launch browser
2. Run update.html 
(ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/2001-05-24-09-trunk/
update.html)
3. After successfully updating, leave the browser open

RESULT:
After about 20 min, a crash occurs.

I think this would affect the success of website because nobody should feel 
comfortable with a product that has crashed after updating.  And I believe this 
could affect many with slower modems like 56K since it seems that it would not 
be uncommon to start an update and return much later.

I will try to narrow down where download UI broke.

EXPECTED RESULT:
No crash.  Browser needs to be exited and restarted.

Incident ID 30873902

Stack Trace
nsXPInstallManager::OnStatus 
[d:\builds\seamonkey\mozilla\xpinstall\src\nsXPInstallManager.cpp, line 852] 
nsFTPChannel::OnStatus 
[d:\builds\seamonkey\mozilla\netwerk\protocol\ftp\src\nsFTPChannel.cpp, line 
431] 
nsFtpState::StopProcessing 
[d:\builds\seamonkey\mozilla\netwerk\protocol\ftp\src\nsFtpConnectionThread.cpp, 
line 1776] 
nsFtpState::Process 
[d:\builds\seamonkey\mozilla\netwerk\protocol\ftp\src\nsFtpConnectionThread.cpp, 
line 584] 
nsFtpState::OnDataAvailable 
[d:\builds\seamonkey\mozilla\netwerk\protocol\ftp\src\nsFtpConnectionThread.cpp, 
line 406]

Comment 1

[Jimmy Lee]

Adding keywords crash and nsbeta1.  Nominating for Beta.  This impacts all that 
are updating to the next point release from website.  It is difficult for me to 
measure how many users may encounter this.  But it is certain it will occur if 
users do leave their browsers open after updating.  I found this by accident, 
but it still happened.  I'll try to find more info.

Comment 2

[Matthias Versen [:Matti]]

*** Bug 82629 has been marked as a duplicate of this bug. ***

Comment 3

[Jimmy Lee]

Build 2001-03-20-06-Mtrunk(WIN) does not have a working progress meter.  Build 
2001-02-15-10-M0.8(WIN) does work.

Comment 4

[Jimmy Lee]

Build: 2001-06-05-03-0.9.1(MAC), 2001-06-05-04-0.9.1(LINUX), 
2001-06-05-11-0.9.1(WIN)

This is still reproducible. :-(

Comment 5

[Jeremy Loeb (gone)]

i think this is a beta stopper... but that's just my opinion :). makes us look 
bad. i know people have to reatart the browser anyway, but let's let them know 
that in a civil manner. not by crashing their browser on them!

Comment 6

[Grace Bush]

If you use SmartUpdate, the completion page reminds you to restart browser- 

Comment 7

[Asa Dotzler [:asa]]

pushing out. 0.9.2 is done. (querying for this string will get you the list of
the 0.9.2 bugs I moved to 0.9.3)

Comment 8

[Blake Ross]

Missed 0.9.3.

Comment 9

[Daniel Veditz [:dveditz]]

I'll investigate... This could be a case of the AIM registry getting regenerated
or something along those lines. We may need to do the "delete file later"
feature after all.

Comment 10

[Syd Logan]

Dan sez "Dupe of topcrash 85307, which was fixed." 

*** This bug has been marked as a duplicate of 85307 ***

Comment 11

[Jimmy Lee]

Bug 85307 has been verified.  Marking this one verified!