Crash in [@ mozilla::CrashOnDanglingCheckedUnsafePtr::NotifyCheckFailure]
Categories
(Core :: Storage: StorageManager, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox105 | --- | unaffected |
firefox106 | + | disabled |
firefox107 | --- | disabled |
People
(Reporter: aryx, Assigned: edenchuang)
References
Details
(Keywords: crash, regression, topcrash)
Crash Data
22 crashes for Firefox v106 and v107, on many different devices and operating systems
Crash report: https://crash-stats.mozilla.org/report/index/a871c900-9aa3-44ee-961f-48ceb0220922
MOZ_CRASH Reason: MOZ_CRASH(Found dangling CheckedUnsafePtr)
Top 10 frames of crashing thread:
0 xul.dll mozilla::CrashOnDanglingCheckedUnsafePtr::NotifyCheckFailure dom/quota/CheckedUnsafePtr.h:247
0 xul.dll mozilla::CheckingPolicyAccess::NotifyCheckFailure dom/quota/CheckedUnsafePtr.h:215
0 xul.dll mozilla::CheckCheckedUnsafePtrs<mozilla::CrashOnDanglingCheckedUnsafePtr>::Check dom/quota/CheckedUnsafePtr.h:239
0 xul.dll mozilla::detail::SupportCheckedUnsafePtrImpl<mozilla::CrashOnDanglingCheckedUnsafePtr, mozilla::CheckingSupport::Enabled>::~SupportCheckedUnsafePtrImpl dom/quota/CheckedUnsafePtr.h:284
1 xul.dll mozilla::dom::WorkerPrivate::Release dom/workers/WorkerPrivate.h:142
1 xul.dll mozilla::RefPtrTraits<mozilla::dom::WorkerPrivate>::Release mfbt/RefPtr.h:50
1 xul.dll RefPtr<mozilla::dom::WorkerPrivate>::ConstRemovingRefPtrTraits<mozilla::dom::WorkerPrivate>::Release mfbt/RefPtr.h:381
1 xul.dll RefPtr<mozilla::dom::WorkerPrivate>::assign_assuming_AddRef mfbt/RefPtr.h:69
1 xul.dll RefPtr<mozilla::dom::WorkerPrivate>::operator= mfbt/RefPtr.h:168
1 xul.dll mozilla::dom::WorkerPrivate::ClearSelfAndParentEventTargetRef dom/workers/WorkerPrivate.h:165
Comment 1•2 years ago
|
||
I think this is something Eden is looking at.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
The bug is marked as tracked for firefox106 (beta). However, the bug still isn't assigned.
:jstutte, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit auto_nag documentation.
Comment 3•2 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 content process crashes on beta
For more information, please visit auto_nag documentation.
Comment 4•2 years ago
|
||
This is a reminder regarding comment #2!
The bug is marked as tracked for firefox106 (beta). We have limited time to fix this, the soft freeze is in 10 days. However, the bug still isn't assigned.
Comment 5•2 years ago
|
||
This is a reminder regarding comment #2!
The bug is marked as tracked for firefox106 (beta). We have limited time to fix this, the soft freeze is in 9 days. However, the bug still isn't assigned.
Comment 6•2 years ago
|
||
This is a reminder regarding comment #2!
The bug is marked as tracked for firefox106 (beta). We have limited time to fix this, the soft freeze is in 8 days. However, the bug still isn't assigned.
Comment 7•2 years ago
|
||
We stopped crashing after beta 6 which coincides with the end of our early betas which contain experimental features.
Comment 8•2 years ago
|
||
(In reply to Pascal Chevrel:pascalc from comment #7)
We stopped crashing after beta 6 which coincides with the end of our early betas which contain experimental features.
Yes, despite the signature saying just MOZ_CRASH
these are bound to MOZ_DIAGNOSTIC_ASSERT_ENABLED
.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Comment 9•2 years ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit auto_nag documentation.
Comment 10•1 year ago
|
||
The bug is linked to a topcrash signature, which matches the following criteria:
- Top 10 content process crashes on beta
- Top 5 desktop browser crashes on Mac on beta
For more information, please visit auto_nag documentation.
Updated•1 year ago
|
Comment 11•1 year ago
|
||
I found a couple of new signatures
Assignee | ||
Comment 12•1 year ago
|
||
Since the crash signature are almost the same with bug 1752856, set this as a duplicate to 1752856.
There is a landing patch on 1752856, and I set it as leave-open for tracking the new crash reports after the patch landed.
Description
•