Closed Bug 1115540 Opened 9 years ago Closed 9 years ago

crash [OOM | small] in js::gc::Arena::finalize<JSObject>(js::FreeOp*, js::gc::AllocKind, unsigned int) (Reason: EXCEPTION_BREAKPOINT)

Categories

(Core :: JavaScript: GC, defect)

Product:
Core
Component:
JavaScript: GC
Version:
35 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1115929

People

(Reporter: marvinhk, Unassigned)

Details

(Keywords: crash)

Crash Data

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20141222200458

Steps to reproduce:

login gmail and facebook
auto refresh page every 5 mins with reloadevery
leave the browser ideal


Actual results:

crash [OOM | small] in nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_CopyWithMemutils>::EnsureCapacity (Reason: EXCEPTION_BREAKPOINT)

bug report: bp-2ede302f-771c-4f3a-ab6e-7daa32141225
Crash Signature: [@ OOM | small ] [@ mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xrealloc | nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_CopyWithMemutils>::EnsureCapacity(unsigned int, unsigned int) | XPCWrappedNative::FlatJSObj…
Keywords: crash
Summary: crash [OOM | small] in nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_CopyWithMemutils>::EnsureCapacity (Reason: EXCEPTION_BREAKPOINT) → crash [OOM | small] in js::gc::Arena::finalize<JSObject>(js::FreeOp*, js::gc::AllocKind, unsigned int) (Reason: EXCEPTION_BREAKPOINT)
It doesn't make sense to attribute OOM|small to any function, that's why it has a generic signature for all of those in the first place. It means that we had so little memory available that we ran Out Of Memory (OOM) with a small allocation of <256KB. There's nothing specific to what's at the top of the stack. If you have reliable (!) step to reproduce OOM|small crashes, we are very interested in those, though.
The steps to reproduce are the only interesting thing here, esp. if they work reliably. I'm not sure if we send a memory reports with those crashes right now, but that would also be helpful so we can find out what fills up all the memory.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Crash Signature: [@ OOM | small ] [@ mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xrealloc | nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_CopyWithMemutils>::EnsureCapacity(unsigned int → [@ mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xrealloc | nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_CopyWithMemutils>::EnsureCapacity(unsigned int
You need to log in before you can comment on or make changes to this bug.