Open Bug 1686795 Opened 4 years ago Updated 3 years ago

about:memory fails on content processes with large leaks on macOS

Categories

(Toolkit :: about:memory, defect, P2)

defect

Tracking

()

People

(Reporter: jrmuizel, Unassigned)

Details

On macOS I see two content processes that have 27-28GB of memory. When trying to run about:memory I get "WARNING: the 'heap-allocated' memory reporter does not work for this platform and/or configuration..."

The content processes that don't have large amount of leaks don't give this message.

That's strange. I'm familiar with one issue we have where if a process is really overloaded then it won't finish the memory report within a timeout and we get no report at all, but it sounds like in this case you are getting a report for the process, but it is missing the heap-allocated field.

It looks like aboutMemory.js generates this message when the heap-allocated field is not present. The value gets calculated in jemalloc, and passed into the memory reporter in JemallocHeapReporter::CollectReports().

I assume this is a regular build, and not something weird like ASan or PHC, as that could cause issues.

Could you attach a memory report that has this issue if you have one handy? Thanks.

Severity: -- → N/A
Flags: needinfo?(jmuizelaar)
Priority: -- → P2

Unfortunately, I don't have the memory report and Firefox has since been restarted. If it happens again I'll attach it.

Flags: needinfo?(jmuizelaar)

Changing severity to S4 because N/A results in autonag emails.

Severity: N/A → S4
You need to log in before you can comment on or make changes to this bug.