Closed
Bug 1695132
Opened 4 years ago
Closed 4 years ago
Crash in [@ OOM | small]
Categories
(Core :: IPC, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1673778
People
(Reporter: worcester12345, Unassigned)
Details
(Keywords: crash)
Crash report: https://crash-stats.mozilla.org/report/index/9434162a-88f6-41b4-935c-e1c5b0210211
MOZ_CRASH Reason: MOZ_CRASH()
Top 10 frames of crashing thread:
0 mozglue.dll mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33
1 mozglue.dll mozalloc_handle_oom memory/mozalloc/mozalloc_oom.cpp:51
2 mozglue.dll moz_xmalloc memory/mozalloc/mozalloc.cpp:54
3 xul.dll Pickle::WriteInt64 ipc/chromium/src/base/pickle.cc:582
4 xul.dll mozilla::ipc::WriteIPDLParam<const mozilla::VsyncEvent&> ipc/glue/IPDLParamTraits.h:63
5 xul.dll mozilla::dom::PVsyncParent::SendNotify ipc/ipdl/PVsyncParent.cpp:57
6 xul.dll mozilla::dom::VsyncParent::DispatchVsyncEvent dom/ipc/VsyncParent.cpp:63
7 xul.dll mozilla::detail::RunnableMethodImpl< xpcom/threads/nsThreadUtils.h:1201
8 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1200
9 xul.dll mozilla::ipc::MessagePumpForNonMainThreads::Run ipc/glue/MessagePump.cpp:332
Updated•4 years ago
|
Component: General → IPC
Product: Firefox → Core
Comment 1•4 years ago
|
||
Several of these crashes have been duped to Bug 1673778 - Crash in [@ OOM | small]
Reporter | ||
Comment 2•4 years ago
|
||
When bugs get "duped", do all the comments and information go to the bug they "dupe to"? Or do they just get lost forever?
Comment 3•4 years ago
|
||
(In reply to Worcester12345 from comment #2)
When bugs get "duped", do all the comments and information go to the bug they "dupe to"? Or do they just get lost forever?
They always exist here in bugzilla - they are not lost.
There's not value in filing multiple bugs for the same signature, unless you have different, unique steps to reproduce for a specific stack below the crash signature.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Updated•4 years ago
|
Crash Signature: [@ OOM | small]
You need to log in
before you can comment on or make changes to this bug.
Description
•