Closed
Bug 1492491
Opened 6 years ago
Closed 6 years ago
Crash makes profile unusable until deleting cache2
Categories
(Core :: Security: PSM, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1490585
Tracking | Status | |
---|---|---|
firefox64 | --- | affected |
People
(Reporter: Matti, Unassigned)
References
Details
I'm using Firefox trunk on windows 10
While opening a Bugzilla bug link from Thunderbird in Firefox I got a crash.
From that moment Firefox always crashed on startup, safemode didn't helped and Firefox62 also crashed with that profile.
This happened on my laptop and I used the "refresh" function to repair the profile.
[@ Gecko_SetLengthString ]
bp-7c975ba2-fcf1-4705-a89c-742ad0180918
bp-1b3f937e-80da-4ff2-a668-624220180918
bp-4fcb89d0-69fa-49b3-8cc0-94bc00180918
A few hours later got the same crash on my Desktop system
I fixed that Firefox user profile with renaming the "cache2" directory.
[@ nsSSLStatus::~nsSSLStatus ]
bp-09d30fd7-9ff7-45b0-8755-d25970180919
bp-b621661b-d26d-43c6-a314-b6f8e0180919
bp-cbf320b0-ea1e-43c8-ae9d-da20b0180919
Comment 1•6 years ago
|
||
Woo... this sounds serious. Do you also have the original profile that was causing the first set of crashes? I would be very interested in trying this locally with at least the cache2 faulty directory, would you be willing to provide it?
Flags: needinfo?(bugzilla)
Comment 2•6 years ago
|
||
I'm pretty sure this is a duplicate of Bug 1490585. Keeler, can you confirm?
Flags: needinfo?(dkeeler)
Comment 3•6 years ago
|
||
Almost certainly.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(dkeeler)
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•6 years ago
|
||
I have the "broken" cache2 directory but it seems that it's no longer necessary.
bug 1490585 is marked security/confidential and that explains why I didn't find anything about it :-)
Flags: needinfo?(bugzilla)
Comment 5•6 years ago
|
||
(In reply to Matthias Versen [:Matti] from comment #4)
> I have the "broken" cache2 directory but it seems that it's no longer
> necessary.
> bug 1490585 is marked security/confidential and that explains why I didn't
> find anything about it :-)
I was not aware too. thanks! :)
You need to log in
before you can comment on or make changes to this bug.
Description
•