Closed Bug 1534202 Opened 1 year ago Closed 1 year ago

Crash in [@ mozilla::dom::indexedDB::AsyncDeleteFile]


(Core :: Storage: IndexedDB, defect, P2)




Tracking Status
firefox-esr60 --- unaffected
firefox65 --- unaffected
firefox66 --- unaffected
firefox67 --- fixed
firefox68 --- fixed


(Reporter: calixte, Assigned: janv)


(Blocks 1 open bug)


(Keywords: crash, regression)

Crash Data


(1 file)

This bug is for crash report bp-468542c1-90d1-4927-a6cd-1acf90190310.

Top 10 frames of crashing thread:

0 XUL mozilla::dom::indexedDB::AsyncDeleteFile dom/indexedDB/ActorsParent.cpp:15765
1 XUL mozilla::dom::indexedDB::FileInfo::UpdateReferences dom/indexedDB/FileInfo.cpp:167
2 XUL mozilla::dom::indexedDB:: dom/indexedDB/FileInfo.h:37
3 XUL mozilla::dom::indexedDB:: dom/indexedDB/ActorsParent.cpp:5967
4 XUL mozilla::dom::indexedDB::PBackgroundIDBDatabaseParent::DeallocSubtree ipc/ipdl/PBackgroundIDBDatabaseParent.cpp:740
5 XUL mozilla::dom::indexedDB::PBackgroundIDBFactoryParent::DeallocSubtree ipc/ipdl/PBackgroundIDBFactoryParent.cpp:354
6 XUL mozilla::ipc::PBackgroundParent::DeallocSubtree ipc/ipdl/PBackgroundParent.cpp:4302
7 XUL mozilla::ipc::PBackgroundParent::OnChannelError ipc/ipdl/PBackgroundParent.cpp:3765
8 XUL mozilla::detail::RunnableMethodImpl<mozilla::ipc::MessageChannel*, void  xpcom/threads/nsThreadUtils.h:1122
9 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1179

There is 1 crash in nightly 67 with buildid 20190310095404. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1526891.


Flags: needinfo?(jvarga)
Blocks: 1517090
Assignee: nobody → jvarga
Flags: needinfo?(jvarga)
Priority: -- → P1
Crash Signature: [@ mozilla::dom::indexedDB::AsyncDeleteFile] → [@ mozilla::dom::indexedDB::AsyncDeleteFile] [@ mozilla::dom::indexedDB::`anonymous namespace'::QuotaClient::AsyncDeleteFile]
Component: DOM: Quota Manager → DOM: IndexedDB
Priority: P1 → P2

Jan, will this get fixed in time for uplift to 67?

Flags: needinfo?(jvarga)

Well, the crash volume seems to be low, so the priority has been lowered to P2.
I have some P1s that need to be fixed for 67, then I get back to this bug.
Anyway, I still believe this bug will get fixed in time for uplift to 67.

Flags: needinfo?(jvarga)
Pushed by
Don't schedule a file deletion after quota client shutdown; r=asuth
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68

Comment on attachment 9053736 [details]
Bug 1534202 - Don't schedule a file deletion after quota client shutdown; r=asuth

Beta/Release Uplift Approval Request

  • Feature/Bug causing the regression: Bug 1526891
  • User impact if declined: Users experience crashes. However the volume is not very high.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Minimal patch, verified on Nightly, covered by tests and we are still quite early in the cycle.
  • String changes made/needed: None
Attachment #9053736 - Flags: approval-mozilla-beta?

Looks good, doesn't happen on Nightly anymore.

Comment on attachment 9053736 [details]
Bug 1534202 - Don't schedule a file deletion after quota client shutdown; r=asuth

Crash fix, minimal patch, uplift approved for 67 beta 8, thanks.

Attachment #9053736 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.