Comment 37 for bug 286366

(In reply to comment #14)
> XPCOM, actually. And confirming based on prevalence of similar crashes in
> crash-stats.

Cool.

> Brian, this particular crash looks like it can only happen when your machine
> runs out of memory...

Hrm. _Memory_ or VM? To Firefox (i.e. a userspace app) it should be the same thing, right?

> How much RAM do you have?

$ cat /proc/meminfo
MemTotal: 2851356 kB
MemFree: 83000 kB
Buffers: 111924 kB
Cached: 527796 kB
SwapCached: 162904 kB
Active: 2136748 kB
Inactive: 374328 kB
HighTotal: 1964992 kB
HighFree: 7664 kB
LowTotal: 886364 kB
LowFree: 75336 kB
SwapTotal: 3145720 kB
SwapFree: 2582716 kB
Dirty: 1020 kB
Writeback: 0 kB
AnonPages: 1867844 kB
Mapped: 130508 kB
Slab: 195464 kB
SReclaimable: 71900 kB
SUnreclaim: 123564 kB
PageTables: 8232 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 4571396 kB
Committed_AS: 3758232 kB
VmallocTotal: 110584 kB
VmallocUsed: 61080 kB
VmallocChunk: 49136 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 4096 kB
DirectMap4k: 880640 kB
DirectMap4M: 36864 kB

So, 2.8G total, 80MB currently free, of physical memory, but 3G total and 2.5G free of swap.

Why would additional memory requirements not be satisfied by swapping? I recognize that unless you know of some specific limitations that Firefox is imposing on swapability, you can't really know why swap is not being used.

> Maybe try closing some of your
> other programs until we can figure out a way to keep OOM from crashing you.

Indeed. Or discover why swap is not being utilized to deal with this OO(physical)M.