Closed
Bug 121619
Opened 23 years ago
Closed 23 years ago
Mozilla crash corrupted component.reg => Mozilla cannot be started again
Categories
(Core :: XPCOM, defect)
Tracking
()
People
(Reporter: vincent.deconinck, Assigned: dougt)
Details
Attachments
(1 file)
129.37 KB,
application/octet-stream
|
Details |
From Bugzilla Helper: User-Agent: Mozilla/4.77 [en] (Win98; U) BuildID: 2002012304 On my heavy loaded Win98 PC (Moz + IE + NS4.77 + a few Java VMs with only 128 Mb RAM), Mozilla crashed the system (endless Blue Sceens Of Death) - no talkback. But OK, I am the one to blame as one shouldn't overload a Microsoft OS in such a way. Unfortunately, upon reboot, Mozilla wouldn't restart, crashing everytime I tried with a standard Windows dialog-box (This program has performed an illegal operation ... The full text is reproduced at the end of the report). To diagnose whether the problem was with my profile or with the bin/ directory, I re-unzipped the nightly in another dir and renamed it, and Mozilla started again. Looking further by comparing all the files (thanks cygwin), I noticed that bin/component.reg had changed. I thus restored that file from the freshly unzipped dir to the original one and Mozilla started again, so obviously the first crash had left component.reg in such a state that it crashed Mozilla on startup, leaving the user in a deadlock... Maybe a quick test on component.reg's status would be helpful... -- Here are the details of the windows message (in french, sorry): MOZILLA a causé une défaillance de page dans le module MSVCRT.DLL à 017f:7800272e. Registres : EAX=ffffffff CS=017f EIP=7800272e EFLGS=00010246 EBX=00000000 SS=0187 ESP=0064f348 EBP=0064f378 ECX=00000000 DS=0187 ESI=0064f368 FS=503f EDX=00000001 ES=0187 EDI=007a0d30 GS=0000 Octets à CS : EIP : 8b 01 ba ff fe fe 7e 03 d0 83 f0 ff 33 c2 83 c1 État de la pile : 60f9bb45 00000000 007a0d30 60fbc889 00000000 ffffffff 00000001 0079da90 60fd8094 00000000 ffffffff 00000001 0064f3a0 60fbce5b 00000000 60fd7dac Reproducible: Always Steps to Reproduce: 1. Put a corrupt component.reg (attached, zipped) in the bin dir. 2. Try to launch Mozilla Actual Results: Crash Expected Results: Mozilla could detect it wasn't shut down properly last time it ran, and run a few tests so that corrupt files are repaired or restored... This bug is not about the first crash, but about the fact that if Mozilla is not shut down properly (the cause may have nothing to do with Mozilla), it can result in the impossibility to start it up the again afterwards...
Reporter | ||
Comment 1•23 years ago
|
||
Comment 2•23 years ago
|
||
Reporter: Please always set the severity level to "critical" for crashes.
Reporter | ||
Updated•23 years ago
|
Severity: normal → critical
Comment 3•23 years ago
|
||
->installer
Assignee: asa → dveditz
Component: Browser-General → Installer
QA Contact: doronr → bugzilla
Comment 4•23 years ago
|
||
not installer... xpapps perhaps?
Assignee: dveditz → trudelle
Component: Installer → XP Apps
QA Contact: bugzilla → sairuh
Comment 5•23 years ago
|
||
->XPCOM Registry. Somebody's not calling flush on the registry most likely, after install time there shouldn't be anyone writing to this file.
Assignee: trudelle → dougt
Status: UNCONFIRMED → NEW
Component: XP Apps → XPCOM Registry
Ever confirmed: true
QA Contact: sairuh → dougt
Assignee | ||
Comment 6•23 years ago
|
||
this sounds like a duplicate. *** This bug has been marked as a duplicate of 72518 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•