Closed
Bug 482274
Opened 15 years ago
Closed 6 years ago
XPC.mfl corruption makes Firefox crash on startup
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: Noah, Unassigned)
Details
(Keywords: crash, testcase)
Attachments
(1 file)
410.03 KB,
application/octet-stream
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090226 Firefox/3.0 Build Identifier: I'm reporting on the behalf of a 3.0.7 user on Vista where Firefox kept crashing on startup. He also got the crash reporter when trying to run Safe mode, open profile manager, and even when the default profile was removed to force Firefox to create a new one. Then later in my troubleshooting, everytime I tried to startup Firefox instead of getting the crash dialog, I'd get the 'Firefox is already running' message. I followed the article below to no resolution. http://support.mozilla.com/en-US/kb/Firefox+is+already+running+but+is+not+responding I was getting the 'Firefox is already running' message but no firefox.exe was to be found in Task Manager > Processes, and no parent.lock file in the profile either. After showing the devs his crash report: bp-1dc5a2e0-786e-4675-a6d8-c43cb2090307 I was advised to delete his XPC.mfl, which was the only file in the directory strangely enough, and that resolved the issue. The corrupt XPC.mfl was blocking the creation of XUL.mfl, urlclassifier3.sqlite and the Cache folder. I'm wondering how these 3 were deleted in any case. I'm attaching the corrupt XPC.mfl, it may help you guys. Reproducible: Always
Reporter | ||
Comment 1•15 years ago
|
||
Comment 2•6 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
Updated•6 years ago
|
Resolution: INACTIVE → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•