This bug was filed from the Socorro interface and is report bp-ce298444-38fe-471a-b0c1-65ab32151008. =============================================================
Crash Signature: [@ OOM | unknown | js::CrashAtUnhandlableOOM(char const*) | .LFE5] → [@ OOM | unknown | js::CrashAtUnhandlableOOM(char const*) | .LFE5] [@ OOM | unknown | js::CrashAtUnhandlableOOM | .LFE5]
The following page crashed Firefox three times today, the Flash plugin process once, and Chrome once. The STR is something like quickly scrolling the page or leaving it open for a few minutes. Before the crashes, I saw gfx artifacts from layer tiling. http://memory-alpha.wikia.com/wiki/In_the_Pale_Moonlight_%28episode%29 bp-8761e804-0b32-4367-ae1d-77fb12151030 bp-8c9eaa27-c731-46b5-9e59-a6e8e2151030 bp-d872f049-9e34-4ba5-92be-e8c522151030
The stack reported on crash stat does not make much sense to me, but the issue located under: js::jit::MResumePoint::New js::LifoAlloc::getOrCreateChunk js::jit::MPhi::New js::jit::MBasicBlock::addPredecessorPopN js::jit::MBasicBlock::inherit js::jit::MBasicBlock::addPredecessor got fixed, and this OOM is now handled properly. (In reply to Chris Peterson [:cpeterson] from comment #1) > Before the crashes, I saw gfx > artifacts from layer tiling. This is usually what happens when we are running out of memory, unfortunately.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.