Closed Bug 158287 Opened 24 years ago Closed 23 years ago

During system startup, Mozilla crashes

Categories

(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: superbiskit, Assigned: law)

Details

(Keywords: crash, stackwanted)

Attachments

(1 file)

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020718 BuildID:2002071804 Since downloading this build, Mozilla crashes ALWAYS when started during logon processing. TB8438976W TB8468651Y
Reporter: Have you installed Mozilla over an older build ? If yes do this : uninstall mozilla, delete all files in c:\programs\Mozilla.org\Mozilla\ (but save your plugins) and reinstall mozilla. If you still see the problem try "mozilla -profilemanager" and create an additional test profile.
Severity: normal → critical
Keywords: crash, stackwanted
crash1 TB8438976W nsXULElement::InsertBefore [c:/builds/seamonkey/mozilla/content/xul/content/src/nsXULElement.cpp, line 985] nsImageBoxFrame::AttributeChanged [c:/builds/seamonkey/mozilla/layout/xul/base/src/nsImageBoxFrame.cpp, line 277] NS_NewImageBoxFrame [c:/builds/seamonkey/mozilla/layout/xul/base/src/nsImageBoxFrame.cpp, line 251] PL_InitEvent [c:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, line 571] PL_ProcessPendingEvents [c:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, line 517] DllMain [c:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, line 1043] nsAppShellService::Run [c:/builds/seamonkey/mozilla/xpfe/appshell/src/nsAppShellService.cpp, line 452] main1 [c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1472] main [c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1808] WinMain [c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1826] WinMainCRTStartup() KERNEL32.DLL + 0x7903 (0x77e87903) crash 2 TB8468651Y nsXULElement::InsertBefore [c:/builds/seamonkey/mozilla/content/xul/content/src/nsXULElement.cpp, line 985] nsImageBoxFrame::AttributeChanged [c:/builds/seamonkey/mozilla/layout/xul/base/src/nsImageBoxFrame.cpp, line 277] NS_NewImageBoxFrame [c:/builds/seamonkey/mozilla/layout/xul/base/src/nsImageBoxFrame.cpp, line 251] PL_InitEvent [c:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, line 571] PL_ProcessPendingEvents [c:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, line 517] DllMain [c:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, line 1043] nsAppShellService::Run [c:/builds/seamonkey/mozilla/xpfe/appshell/src/nsAppShellService.cpp, line 452] main1 [c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1472] main [c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1808] WinMain [c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1826] WinMainCRTStartup() KERNEL32.DLL + 0x7903 (0x77e87903)
Responding to Comment#2 >Reporter: >Have you installed Mozilla over an older build ? Yes, the last 4 or 5 times. I thought that had been fixed. Guess not. > If yes do this : > uninstall mozilla, delete all files in c:\programs\Mozilla.org\Mozilla\ (but > save your plugins) and reinstall mozilla. Did it, it didn't help > If you still see the problem try "mozilla -profilemanager" and create an > additional test profile. Well, that created one major PITA. After much messing about, I got to where my "new" profile was pointed at my "old" data. Doing otherwise would cost me a week of work trying to recover my mailfiles. When Moz. first launched into MailNews, it didn't see my existing mail accounts. At first I figured it was because of creating a new profile. That has happened before and locating the correct directories fixed it. The "Create Mail Account" dialog first asked for my name, e.g. John W. Smith. When I entered mine I got an error "Please enter a valid email address". No entry in the "Name" input was acceptable. Finally, I pulled in a backup "prefs.js" from my own recovery method; I diff'd it against the "prefs.bak" and collected whatever new entries seemed to make sense. Launching MailNews now sees my existing mail. I DIDN't SEE ANYTHING IN THE DIFFS THAT SEEMED CONNECTED. But, what the hay, it works. I'll check the Create Mail function later.
Continuing to follow up: the new profile (with the restored prefs.js) seems to have overcome the bug.
Regretably, I over-wrote the non-working "prefs.js" when I restored.
Attachment #92095 - Attachment mime type: application/JavaScript → text/plain
this looks suspiciously like side effects of bug 155080- saw these symptoms when trying to reproduce that bug No crash at startup though
David, Have you been able to install newer builds? Any more problems? Is this no longer an issue for you?
Haven't seen it at all lately. WORKSFORME Thanks for the reminder.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
verified
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: