MEMORYSTATUSEX.ullAvailPageFile tells us how much space is available in physical memory plus the page file.
When this gets to 0, Windows will not let us map any more memory. So we should raise a low-memory event before we get here.
See also bug 720444, where we added ullAvailPageFile to crash reports.
Created attachment 603434 [details] [diff] [review]
I need to add a line to telemetryping.js to send this memory reporter.
Created attachment 603583 [details] [diff] [review]
Try run for 5377fc9154a5 is complete.
Detailed breakdown of the results available here:
Results (out of 50 total builds):
Builds (or logs if builds failed) available at:
Timed out after 06 hours without completing.
Landed on m-i
but this had the wrong bug number (gah), so backed out and re-landed
I think this might be covered elsewhere, but I can't find it. Why is the checking for low physical, commit and virtual memory Windows-only?
(In reply to Daniel Cater from comment #8)
> I think this might be covered elsewhere, but I can't find it. Why is the
> checking for low physical, commit and virtual memory Windows-only?
Because it's hard(er) to do elsewhere, and because it's not a clear win on Windows, so we wanted to do it there before wasting our time elsewhere.
Also, Windows machines are much more likely to be running a 32-bit Firefox than Mac or Linux.