1056451 - crash in mozalloc_abort(char const* const) | NS_DebugBreak | nsPresArena::Allocate(unsigned int, unsigned int)

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[alex_mayorga]

This bug was filed from the Socorro interface and is 
report bp-af3b6960-fa8d-490b-8d02-9434f2140814.
=============================================================

Comment 1

[Mats Palmgren (inactive)]

This is an intentional abort due to a failed memory allocation b/c the system
is running low on memory.  It's not a bug.

Comment 2

[Roman]

Would this crash be resolved by a 64-bit Firefox build? My crash report states that there were 3 GB of free physical RAM at the time of the crash.

Comment 3

[Mats Palmgren (inactive)]

> My crash report states that there were 3 GB of free physical RAM at the time of the crash.

Then your crash is a different problem than the one here.

Do you have a Crash Report ID for your crash? (load about:crashes in the URL bar)

Comment 4

[Roman]

@Mats: yes, https://crash-stats.mozilla.com/report/index/820d307c-0eb7-4fc8-b0f9-ab46d2141028

I don't see why this can't be the case; I do have 3GB of free physical RAM there, but Firefox can't use it being a 32-bit process, because it has consumed most of its 32-bit address space at this point.

Comment 5

[Mats Palmgren (inactive)]

Yes, it looks like the process is running out of 32-bit address space when
the allocation failed.  This shouldn't happen unless you have a very large
number of tabs/windows open.  Most likely there is a memory leak somewhere.
It could be Firefox itself, or one of your add-ons if you have those, or
simply that a page in one of the tabs is holding on to memory.

I would recommend that you first upgrade to Firefox 36 or later,
disable or remove add-ons you don't need and then, if the problem
still occurs, file a new bug report with the contents of about:memory
attached.  You have to make the copy of about:memory before it crashes
obviously, so you'd have to monitor Firefox' memory consumption.
That should help us determine which part of the process is using up
most of the memory.  Thanks!