Closed
Bug 1710274
Opened 3 years ago
Closed 3 years ago
Crash in [@ IPCError-browser | ShutDownKill | __GI_madvise]
Categories
(Core :: DOM: Content Processes, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1279293
People
(Reporter: woyece, Unassigned)
Details
Crash Data
Maybe Fission related. (DOMFissionEnabled=1)
Crash report: crash-stats .mozilla . org / report/ index /4644c885-f736-4c9c-a0b1-6bd330210507
Reason: DUMP_REQUESTED
Top 10 frames of crashing thread:
0 libc.so.6 __GI_madvise
1 firefox-bin arena_t::DallocRun memory/build/mozjemalloc.cpp:2635
2 firefox-bin BaseAllocator::realloc memory/build/mozjemalloc.cpp:4114
3 firefox-bin moz_arena_realloc memory/build/malloc_decls.h:135
4 libxul.so mozilla::Vector<char16_t, mfbt/Vector.h:1021
5 libxul.so Str js/src/builtin/JSON.cpp:695
6 libxul.so Str js/src/builtin/JSON.cpp:746
7 libxul.so Str js/src/builtin/JSON.cpp:746
8 libxul.so js::Stringify js/src/builtin/JSON.cpp:924
9 libxul.so json_stringify js/src/builtin/JSON.cpp:1125
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Content Processes' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Component: Untriaged → DOM: Content Processes
Product: Firefox → Core
|
||
Updated•3 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
|
||
Comment 3•3 years ago
|
||
Thanks for the bug report, Woyece. Unfortunately, these "ShutDownKill" crashes are not actionable. They just mean that a Firefox process was taking longer to shutdown than expected and so Firefox killed the process. The crash stack trace just happens to be whatever random code was running at that time.
You need to log in
before you can comment on or make changes to this bug.
Description
•