Closed
Bug 1665295
Opened 4 years ago
Closed 4 years ago
Intermittent ASSERTION: Could not get nsICertStorage: 'NS_SUCCEEDED(rv)', file /home/simon/work/mozilla-unified/xpcom/base/AppShutdown.cpp, line 167
Categories
(Core :: Security: PSM, defect)
Core
Security: PSM
Tracking
()
RESOLVED
FIXED
84 Branch
Tracking | Status | |
---|---|---|
firefox84 | --- | fixed |
People
(Reporter: sg, Assigned: beurdouche)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [psm-assigned])
Attachments
(1 file)
I am hitting the assertion at https://searchfox.org/mozilla-central/rev/30e70f2fe80c97bfbfcd975e68538cefd7f58b2a/xpcom/base/AppShutdown.cpp#167 added in Bug 1648142 occasionally locally.
Reporter | ||
Comment 1•4 years ago
|
||
Actually, I hit this frequently right now. Interestingly, when running mach test
, while there is a crash due to that, it doesn't seem to affect the test result, which is also somewhat confusing.
Updated•4 years ago
|
Assignee: nobody → bbeurdouche
Severity: -- → S4
Whiteboard: [psm-assigned]
Assignee | ||
Comment 2•4 years ago
|
||
Comment 3•4 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:beurdouche, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(bbeurdouche)
Pushed by malexandru@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/39d269f4a596
Remove unnecessary assertion on getting nsICertStorage on AppShutdown. r=keeler
Comment 5•4 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox84:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
Assignee | ||
Updated•4 years ago
|
Flags: needinfo?(bbeurdouche)
Assignee | ||
Comment 7•4 years ago
|
||
Thanks, this was my mistake. I re-marked it as "Check-in-needed" because it was still shown "Accepted" but the patch was already landed by Atila as seen in the comment above.
Flags: needinfo?(bbeurdouche)
Updated•4 years ago
|
Keywords: regression
Updated•4 years ago
|
Has Regression Range: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•