FireFox 57 spectacularly explodes with the amount of requested allocated memory




2 years ago
3 months ago


(Reporter: zxspectrum3579, Unassigned)


57 Branch

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [MemShrink])


(4 attachments)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20180103231032

Steps to reproduce:

Regular browser use for a prolonged time. 
I used, what could have triggered this. But I am not sure, this might be unrelated.

Actual results:

One of the FireFox.exe processes has crashed in an apparent Windows OOM error, hence leaving no traces in either sent or unsent crash errors. The browser has continued to operate once click-to-load tabs loaded the necessary pages anew, however, one of the FireFox.exe processes that were not killed has shown that it has 29 GB of allocated memory, even though it actually used only 1.8 GB, as task manager shows. Soon enough FireFox has deteriorated quickly visually and had to be manually closed to be restarted.

Before the restart, I was able to capture memory snapshot as well as short profiler recording for few seconds to see what the browser was doing in the background while on standby. 

Expected results:

Normal continuous operation.
Component: Untriaged → Memory Allocator
Product: Firefox → Core
Windows-generated warning:

Event 2001, Resource-Exhaustion-Detector:

... for firefox.exe (36400) was allocated 29356462080 bytes, for firefox.exe (28196) was allocated 2371203072 bytes and for firefox.exe (17188) was allocated 2200621056 bytes.


- <Event xmlns="">
- <System>
  <Provider Name="Microsoft-Windows-Resource-Exhaustion-Detector" Guid="{9988748E-C2E8-4054-85F6-0C3E1CAD2470}" /> 
  <TimeCreated SystemTime="2018-01-18T18:13:01.205817000Z" /> 
  <Correlation ActivityID="{DD80558A-632C-48DD-91A4-CE99267E978A}" /> 
  <Execution ProcessID="57020" ThreadID="389352" /> 
  <Security UserID="S-1-5-18" /> 
- <UserData>
- <MemoryExhaustionInfo xmlns="">
- <SystemInfo>
- <PagedPoolInfo>
- <Tag_1>
- <Tag_2>
- <Tag_3>
- <NonPagedPoolInfo>
- <Tag_1>
- <Tag_2>
- <Tag_3>
- <ProcessInfo>
- <Process_1>
- <Process_2>
- <Process_3>
- <Process_4>
  <Name /> 
- <Process_5>
  <Name /> 
- <Process_6>
  <Name /> 
- <ExhaustionEventInfo>
Windows-generated error:

Event 1000:

Name of the failed process: firefox.exe, version:, timespamp: 0x5a4d7442
Name of the failed module: mozglue.dll, version:, timespamp: 0x5a4d73e5
Code of exception: 0x80000003
Error off-set: 0x00000000000138c1
PID: 0x6e24

- <Event xmlns="">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <TimeCreated SystemTime="2018-01-18T19:00:58.038486900Z" /> 
  <Security /> 
- <EventData>
  <Data>C:\Program Files\Mozilla Firefox\firefox.exe</Data> 
  <Data>C:\Program Files\Mozilla Firefox\mozglue.dll</Data> 
  <Data /> 
  <Data /> 

Moving this bug report about memory usage (which is not related to the memory allocator) to Untriaged.

Component: Memory Allocator → Untriaged
Product: Core → Firefox

That's 28GB of private memory coming through our allocator:

28,490.45 MB (100.0%) -- explicit
├──27,513.71 MB (96.57%) ── heap-unclassified

Are you still able to reproduce this?

Flags: needinfo?(zxspectrum3579)
Whiteboard: [MemShrink]

No, this specific phenomenon does not happen any more. I am witnessing a different issue which is about 100%-all-cores-busy CPU load (bug 1553074). So unless someone still has the giant memory use issues, this bug should be probably closed.

Flags: needinfo?(zxspectrum3579)

Okay lets close this for now.

Closed: 3 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.