Open Bug 1473892 Opened Last year Updated 9 months ago
Crash in OOM | unknown | js::Auto
Enter OOMUnsafe Region::crash | js::gc::Store Buffer::Whole Cell Buffer::allocate Cell Set
This bug was filed from the Socorro interface and is report bp-d6a573a5-8c73-4bc4-8143-db8680180706. ============================================================= Seen while looking at crash stats: https://bit.ly/2KUtkEn. These crashes started in 61, and it appears as if some code was touched in Bug 1447385. 1318 crashes in 61.0. It is visible in the 62 betas but in fairly low volume. Top 10 frames of crashing thread: 0 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1587 1 xul.dll js::gc::StoreBuffer::WholeCellBuffer::allocateCellSet js/src/gc/StoreBuffer.cpp:140 2 xul.dll js::gc::StoreBuffer::WholeCellBuffer::put js/src/gc/StoreBuffer-inl.h:75 3 xul.dll js::jit::PostWriteElementBarrier<0> js/src/jit/VMFunctions.cpp:736 4 xul.dll static js::jit::EnterJitStatus EnterJit js/src/jit/Jit.cpp:99 5 xul.dll js::jit::MaybeEnterJit js/src/jit/Jit.cpp:163 6 xul.dll static bool Interpret js/src/vm/Interpreter.cpp:3144 7 xul.dll js::RunScript js/src/vm/Interpreter.cpp:417 8 xul.dll js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:489 9 xul.dll js::Call js/src/vm/Interpreter.cpp:535 =============================================================
Hey Jon, this is currently almost 3% of our content process crashes on Fx61. Any idea what might be going on here?
A quick scan of most of the reports show the predominate locale affected is fr. Seems as if https://www.sfr.fr/ is mentioned in some of the comments.
tentatively marking this as blocking bug 1447385, which would fit into the regression range.
(In reply to Ryan VanderMeulen [:RyanVM] from comment #1) Bug 1447385 changed how we allocate buffers for the whole cell store buffer. It doesn't actually allocate any more memory than before though, so my suspicion is that this has just shifted the OOMs around. Can we tell if the overall OOM rate increased with this change?
you're right, the same issue apparently has showed up as [@ OOM | small] crash before this change, so it's not a real regression. there is a visible spike for [@ OOM | small] content crashes for french builds starting on july 3rd too, so i suspect the SFR webmail site made some changes there introducing the instability/bug: https://crash-stats.mozilla.com/signature/?product=Firefox&useragent_locale=fr&process_type=%3Dcontent&signature=OOM%20%7C%20small&date=%3E%3D2018-05-01#graphs maybe we could reach out to that 3rd-party website?
Maybe Adam can help with reaching out to SFR webmail?
Reaching out to a contact we have from a webcompat issue & trying some new contacts on LinkedIn.
We now have a contact for this issue, included Andrew on the email chain.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.