1903446 - Crash in [@ mozilla::dom::quota::DropDirectoryLock<T>]

Status: RESOLVED DUPLICATE of bug 1903169

(Core :: Storage: Quota Manager, defect, P4)

Description

[BugBot [:suhaib / :marco/ :calixte]]

Crash report: https://crash-stats.mozilla.org/report/index/67630f99-7126-4161-8e89-2c7ed0240616

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0  libxul.so  mozilla::dom::quota::DropDirectoryLock<mozilla::dom::quota::DirectoryLock>  dom/quota/DirectoryLockInlines.h:32
0  libxul.so  mozilla::dom::indexedDB::  dom/indexedDB/ActorsParent.cpp:16740
1  libxul.so  mozilla::dom::indexedDB::  dom/indexedDB/ActorsParent.cpp
2  libxul.so  nsThread::ProcessNextEvent  xpcom/threads/nsThread.cpp:1198
2  libxul.so  NS_ProcessNextEvent  xpcom/threads/nsThreadUtils.cpp:480
3  libxul.so  mozilla::ipc::MessagePumpForNonMainThreads::Run  ipc/glue/MessagePump.cpp:300
4  libxul.so  MessageLoop::RunInternal  ipc/chromium/src/base/message_loop.cc:370
4  libxul.so  MessageLoop::RunHandler  ipc/chromium/src/base/message_loop.cc:363
4  libxul.so  MessageLoop::Run  ipc/chromium/src/base/message_loop.cc:345
4  libxul.so  nsThread::ThreadFunc  xpcom/threads/nsThread.cpp:370

By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:

• First crash report: 2024-06-16
• Process type: Parent
• Is startup crash: No
• Has user comments: No
• Is null crash: Yes - all crashes happened on null or near null memory address

By analyzing the backtrace, the regression may have been introduced by a patch [1] to fix Bug 1883353.

[1] https://hg.mozilla.org/mozilla-central/rev?node=dca9f407ea90

:janv, since you are the author of the potential regressor, could you please take a look?

Comment 1

[Jan Varga [:janv]]

This crash shouldn't happen anymore after https://phabricator.services.mozilla.com/D213917
The diagnostic assertion is being addressed in bug 1903387.