481108 - Firefox hangs then crashes [@ GCGraphBuilder::AddNode]

Status: RESOLVED DUPLICATE of bug 502687

(Firefox :: General, defect)

Description

[Alex Burke]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1
Build Identifier: 

With lots of tabs open, Firefox eventually hangs for a while, then crashes.

Reproducible: Sometimes

Steps to Reproduce:
One window, ~140 tabs open. Box was not out of RAM. Some tabs have Flash in them (such as paused YouTube videos). Firefox was the foreground application this time.
Actual Results:  
Crashed.

Expected Results:  
Not crashed.

See attachments; sample taken while Firefox was hung/beachballed (beach ball, colour wheel, color wheel, whatever).

Comment 1

[Alex Burke]

Attachment: Sample taken with Activity Monitor while hung

Comment 2

[Alex Burke]

Attachment: Raw Dump from Firefox Crash Reporter

Comment 3

[Alex Burke]

Crashed @ GCGraphBuilder::AddNode(void*, nsCycleCollectionParticipant*)

Comment 4

[Alex Burke]

Mar  2 22:25:04 machine-name [0x0-0x14f14f].org.mozilla.firefox[0]: *** error: can't allocate region
Mar  2 22:25:04 machine-name [0x0-0x14f14f].org.mozilla.firefox[0]: *** set a breakpoint in malloc_error_break to debug
Mar  2 22:25:04 machine-name [0x0-0x14f14f].org.mozilla.firefox[0]: firefox-bin(3704,0xa012a720) malloc: *** mmap(size=8388608) failed (error code=12)

Comment 5

[Alex Burke]

Attachment: System Profile (redacted)

Comment 6

[Alex Burke]

/usr/include/sys/errno.h :
#define	ENOMEM		12		/* Cannot allocate memory */

Comment 7

[Alex Burke]

Firefox version is 3.0.6 on Mac OS X 10.5.6 (9G55).

Comment 8

[Marcia Knous [:marcia]]

Please type about:crashes in the URL bar and paste the breakpad crash ID in the bug. Thanks.

Comment 9

[Alex Burke]

Crash ID is 03231778-bc66-4085-aef0-fc82f2090302

Comment 10

[Jesse Ruderman]

bp-03231778-bc66-4085-aef0-fc82f2090302 shows this crashing at precisely the point where I'd expect bug 502687 to occur, and your system profile shows evidence that Firefox ran out of virtual memory.  So this is a dup of bug 502687, which was fixed on trunk last month.

But note that when Firefox is out of memory, it's likely to crash for one reason or another.  You're better off tackling the memory use issue (by helping us find leak bugs or memory use bugs, or by keeping fewer tabs open) than the individual crashes that result.