Crash in [@ mozilla::CrashOnDanglingCheckedUnsafePtr::NotifyCheckFailure]
Categories
(Core :: Storage: IndexedDB, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox124 | --- | unaffected |
firefox125 | --- | unaffected |
firefox126 | + | fixed |
People
(Reporter: mccr8, Assigned: janv)
References
(Regressed 2 open bugs)
Details
(Keywords: crash, regression, topcrash)
Crash Data
Attachments
(3 files, 1 obsolete file)
Crash report: https://crash-stats.mozilla.org/report/index/159eca64-a51c-4c03-a19b-a30f90240326
MOZ_CRASH Reason: MOZ_CRASH(Found dangling CheckedUnsafePtr)
Top 10 frames of crashing thread:
0 libxul.so mozilla::CrashOnDanglingCheckedUnsafePtr::NotifyCheckFailure dom/quota/CheckedUnsafePtr.h:419
0 libxul.so mozilla::CheckingPolicyAccess::NotifyCheckFailure<mozilla::CrashOnDanglingCheckedUnsafePtr> dom/quota/CheckedUnsafePtr.h:387
0 libxul.so mozilla::CheckCheckedUnsafePtrs<mozilla::CrashOnDanglingCheckedUnsafePtr>::Check dom/quota/CheckedUnsafePtr.h:411
0 libxul.so mozilla::detail::SupportCheckedUnsafePtrImpl<mozilla::CrashOnDanglingCheckedUnsafePtr, dom/quota/CheckedUnsafePtr.h:459
1 libxul.so mozilla::dom::indexedDB:: dom/indexedDB/ActorsParent.cpp:3150
2 libxul.so mozilla::dom::indexedDB:: dom/indexedDB/ActorsParent.cpp:3399
3 libxul.so mozilla::Runnable::Release xpcom/threads/nsThreadUtils.cpp:66
3 libxul.so mozilla::dom::indexedDB:: dom/indexedDB/ActorsParent.cpp:14610
4 libxul.so mozilla::RefPtrTraits<mozilla::dom::indexedDB:: mfbt/RefPtr.h:49
4 libxul.so RefPtr<mozilla::dom::indexedDB:: mfbt/RefPtr.h:409
It looks like a bunch of these crashes started showing up on Nightly, with the 20240325214523 build.
Reporter | ||
Comment 1•8 months ago
|
||
[Tracking Requested - why for this release]:
Here are the changesets for that build. I see bug 1878146 and bug 934640 in that range that look potentially related.
Assignee | ||
Comment 2•8 months ago
|
||
Yeah, let me do more investigation...
I don't think it has something to do with bug 1878146.
Assignee | ||
Comment 3•8 months ago
|
||
Assignee | ||
Comment 4•8 months ago
|
||
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Comment 6•8 months ago
|
||
The bug is marked as tracked for firefox126 (nightly). However, the bug still has low severity.
:jstutte, could you please increase the severity for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Comment 7•8 months ago
|
||
IIUC the patch that is landing in comment 5 is already meant to address the problem, so in fact we are in a good shape here.
I also wonder if tracking alone is a sufficient reason for S2, actually. It might be a just hint that this is likely to become S2 if it hits release.
Comment 8•8 months ago
|
||
bugherder |
Assignee | ||
Comment 9•8 months ago
|
||
There will be one more fix.
Assignee | ||
Comment 10•8 months ago
|
||
Assignee | ||
Comment 11•8 months ago
|
||
Comment 12•8 months ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 desktop browser crashes on nightly
:janv, could you consider increasing the severity of this top-crash bug?
For more information, please visit BugBot documentation.
Comment 13•8 months ago
|
||
Comment 14•8 months ago
|
||
bugherder |
Comment 15•8 months ago
|
||
Assignee | ||
Comment 16•8 months ago
|
||
It seems web platforms tests for indexedDB.databases
don't cover the case when indexedDB.databases
and multiple open or delete operations are requested at the same time. Fortunately, based on the crash reports, especially the CheckedUnsafePtr
, we were quickly able to identify the issue. Two fixes and one new test already landed. One more test is about to land (for the interaction with database maintenance). I'm keeping the bug open, until we see that the number of crashes is zero in recent nightly builds.
Comment 17•8 months ago
|
||
bugherder |
Assignee | ||
Comment 18•8 months ago
|
||
There have been no crashes related to the signature after the second fix, so I'll just fix the remaining test to work on Android and that should be it.
Comment 19•8 months ago
|
||
(In reply to Jan Varga [:janv] from comment #18)
There have been no crashes related to the signature after the second fix, so I'll just fix the remaining test to work on Android and that should be it.
Please move the test or any other remaining work to a new bug, as this is a tracked bug we should close it as early as we can.
Comment 20•8 months ago
|
||
Comment on attachment 9393488 [details]
Bug 1888006 - Add a new test for idle daily maintenance and IDBFactory.databases() interaction; r=#dom-storage
Revision D205830 was moved to bug 1890283. Setting attachment 9393488 [details] to obsolete.
Assignee | ||
Updated•8 months ago
|
Updated•8 months ago
|
Updated•8 months ago
|
Description
•