1908574 - Crash in [@ mozilla::dom::ipc::WritableSharedMap::Serialize]

Status: NEW

(Core :: DOM: Content Processes, defect)

Description

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

Crash report: https://crash-stats.mozilla.org/report/index/e6d8229c-e05d-44a7-a391-18b160240702

MOZ_CRASH Reason: MOZ_RELEASE_ASSERT(mem.Finalize(mMap).isOk())

Top 10 frames of crashing thread:

0  libxul.so  mozilla::dom::ipc::WritableSharedMap::Serialize  dom/ipc/SharedMap.cpp:340
1  libxul.so  mozilla::dom::ipc::WritableSharedMap::BroadcastChanges  dom/ipc/SharedMap.cpp:364
2  libxul.so  mozilla::detail::RunnableMethodArguments<>::apply<nsObserverService, void  const  xpcom/threads/nsThreadUtils.h:1085
2  libxul.so  std::__invoke_impl<void, mozilla::detail::RunnableMethodArguments<>::apply<nsObserverService, void   /builds/worker/fetches/sysroot-x86_64-linux-gnu/usr/include/c++/8/bits/invoke.h:60
2  libxul.so  std::__invoke<mozilla::detail::RunnableMethodArguments<>::apply<nsObserverService, void   /builds/worker/fetches/sysroot-x86_64-linux-gnu/usr/include/c++/8/bits/invoke.h:95
2  libxul.so  _ZSt12__apply_implIZN7mozilla6detail23RunnableMethodArgumentsIJEE5applyI17nsObserverServiceMS5_FvvEEEDcPT_T0_EUlDpOT_E_RSt5tupleIJEETpTnmJEEDcOS8_OSA_St16integer_sequenceImJXspT1_EEE  /builds/worker/fetches/sysroot-x86_64-linux-gnu/usr/include/c++/8/tuple:1678
2  libxul.so  std::apply<mozilla::detail::RunnableMethodArguments<>::apply<nsObserverService, void   /builds/worker/fetches/sysroot-x86_64-linux-gnu/usr/include/c++/8/tuple:1687
2  libxul.so  mozilla::detail::RunnableMethodArguments<>::apply<nsObserverService, void   xpcom/threads/nsThreadUtils.h:1083
2  libxul.so  mozilla::detail::RunnableMethodImpl<mozilla::dom::indexedDB::  xpcom/threads/nsThreadUtils.h:1134
3  libxul.so  mozilla::RunnableTask::Run  xpcom/threads/TaskController.cpp:580

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

• First crash report: 2024-06-06
• 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

Comment 1

[Andrew McCreight [:mccr8]]

These have the crash reason MOZ_RELEASE_ASSERT(mem.Finalize(mMap).isOk()). I'm not really sure what that is about.

Comment 2

[Andrew McCreight [:mccr8]]

Crash volume is low.