Closed Bug 1660063 Opened 5 years ago Closed 4 years ago

Crash in [@ mozalloc_abort | moz_xmalloc | IPC::Message::Message]

Categories

(Core :: IPC, defect)

79 Branch
x86
Windows
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox-esr68 --- unaffected
firefox-esr78 --- wontfix
firefox79 --- wontfix
firefox80 --- wontfix
firefox81 --- wontfix
firefox82 --- wontfix

People

(Reporter: philipp, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-aaad471f-30bd-46bb-92bf-b5a850200819.

Top 8 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 IPC::Message::Message ipc/chromium/src/chrome/common/ipc_message.cc:58
4 xul.dll mozilla::dom::PMessagePortChild::SendPostMessages ipc/ipdl/PMessagePortChild.cpp:53
5 xul.dll mozilla::dom::MessagePort::PostMessage dom/messagechannel/MessagePort.cpp:410
6 xul.dll mozilla::dom::MessagePort_Binding::postMessage dom/bindings/MessagePortBinding.cpp:188
7  @0x3036e664 

this windows content crash signature is somewhat increasing in the past ten days - crashing urls in recently submitted reports seem to prominently feature various zoom.us web meeting urls (but there are many other affected domains as well).

This doesn't have an OOM | small annotation, but it appears to be a small allocation (the message header) failing, which typically isn't something we can do anything about: if it's not this allocation, it would probably be another one, and there's no indication that this allocation site is related to why the system is low on memory.

I'm told that sometimes we can fail to record crash annotations in low-memory situations, so that might be why this isn't marked as an OOM in the signature.

It turns out that this allocation isn't exactly small, but it's not large either: bug 1348591 added a facility for changing the initial buffer allocation size, which is used here to set it to 12k.

Still, there isn't a good way to handle allocation failure here, and if we can't allocate 12k then we're probably about to crash somewhere.

The severity field is not set for this bug.
:jld, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jld)

This is a small OOM, and I don't think we can do anything about it.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(jld)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.