Closed Bug 78246 Opened 20 years ago Closed 20 years ago

Crash launching Netscape after running update.html

Categories

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

PowerPC
Mac System 9.x
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.2

People

(Reporter: jimmykenlee, Assigned: slogan)

References

Details

(Keywords: crash, platform-parity, regression, Whiteboard: [smartupdate])

Build: 2001-04-30-09-trunk(MAC)

1. Install 2001-04-30-09-trunk(MAC)
2. Launch and open 
ftp://sweetlou/products/client/seamonkey/macos/8.x/ppc/2001-04-27-14-trunk/updat
e.html
3. Click Launch XPInstall button
4. Click OK from confirm dialog
5. After update is completed, exit Netscape
6. Launch Netscape
7. If Profile dialog appears, select one to open.

RESULT:
Crash.

EXPECTED RESULT:
No crash.  Browser launches gracefully.

NOTE:
Sometimes I crash at exit as well.

TalkBack Incident ID 29829366

Stack Trace
0x564f4400 
NSStdLib + 0x518 (0x1f25f908) 
Netscape 6 + 0x19bac (0x1f2b66dc)
Nominating for Beta.  This test simulates an upgrade from one browser release to 
another.  This is a must fix or users will not be able to update gracefully from 
the website.  This is a mac-only problem.
Keywords: nsbeta1, pp
Here's the info for the crash at quit.

TalkBack Incident ID 29829835

Stack Trace
0xf7dfffc8 
exit() [abort_exit.c] 
Netscape 6 + 0x19bac (0x1f9106dc)
Adding keyword crash.

Also, it was observed than running an update.html from 4/27/01 to 4/30/01 on 
Linux consistently resulted in a crash upon attempting to launch the newly 
updated build.  However, running an update.html from 4/30/01 to 4/27/01 on Linux 
consistently launched with no crash.
Keywords: crash
I was able to update from 5/7/01 to 5/8/01 and successfully launch updated 
build.  It appears to be working now.  However, I'm not sure what may have 
changed to affect this case.
This is probably an issue of not deleting old files. Gotta do it
Keywords: nsbeta1nsbeta1+, regression
Whiteboard: [smartupdate]
Target Milestone: --- → mozilla0.9.1
Depends on: 65678
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Don, 
Dan thought this may be fixed by #65678 (which you just marked as FIXED). Can 
you confirm?
Well, we don't really know the true cause of this but if Jimmy isn't seeing it
anymore and he's testing 65678 then I suppose we can mark this fixed.

Syd, do you agree?  It's assigned to you.
This does seem to work fine now.  The real problems are now going from 6.0 to 
the current release.  But that's another bug altogether.
marking closed based on Jimmy's comments
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Marking Verified! :-)
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.