On 1/6/16 00:51, Nicholas Nethercote wrote:
On Wed, Jun 1, 2016 at 2:37 AM, Jonathan Kew <jfkth...@gmail.com> wrote:
I took a quick look at a random one of these OOMs[1], and what strikes me
about it is that according to the crash report:
Total Virtual Memory 2147352576
Available Virtual Memory 122331136
System Memory Use Percentage 52
Available Page File 4932567040
Available Physical Memory 1790652416
OOM Allocation Size 24
it seems like the system is still some way from running out of memory.
Available Virtual Memory is "only" 122MB, which admittedly isn't very much
in present-day terms, but still....why can't we successfully allocate a
24-byte block? Can those 122MB really be _so_ fragmented?!
I looked at a bunch of these yesterday. It's pretty common for OOM to
occur when there is around 200--250 MiB of available virtual memory;
122 MB is probably lower than normal.
Does this suggest that we're not sufficiently proactive about firing
memory-pressure notifications, so that we'll free up memory from various
caches, etc? It looks like we regard 128MB of available VM as "low" (see
[1]) on Windows 32-bit, but apparently we're liable to suffer small-OOM
crashes well before we reach that point. That doesn't seem like a
healthy balance.
JK
[1]
https://dxr.mozilla.org/mozilla-central/source/xpcom/base/AvailableMemoryTracker.cpp#497-498
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
