Closed Bug 1347227 Opened 7 years ago Closed 6 years ago

High system-heap-allocated memory usage in Firefox 52 when scrolling in Facebook

Categories

(Core :: Graphics, enhancement, P3)

enhancement

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
platform-rel --- -

People

(Reporter: mccr8, Unassigned)

References

Details

(Whiteboard: [MemShrink:P2][platform-rel-Facebook][gfx-noted])

Attachments

(6 files)

(In reply to Jorge Velasco from bug 1346556 comment #90)
> The problems persists in FF 52.0 (32bit) in Windows Vista. As I described
> before, it happens while scrolling down in Facebook News Feed. Memory usage
> grows up to 1.050.000 KB and finally FF stops working. FF doesn't load
> anything else in the page, or it is a long time.
Are you able to get a memory report from about:memory while the memory is rising? How long does it take to cause Firefox to become unresponsive? What addons do you have installed?
Flags: needinfo?(jorgevelascobcn)
Summary: High memory usage when scrolling in Facebook → High memory usage in Firefox 52 when scrolling in Facebook
Whiteboard: [MemShrink]
Attached file memory-report.json.gz
I did this report when FF 52 (32 bit) in Windows Vista had already stopped loading new contents to the facebook News Feed. Two FF processes appear in the task manager: the one uses 990.000 KB and the other 120.000 KB.
Additional information to the attachement.

There was only one tab. It was the facebook News Feed. I scrolled down for eight minutes. Then FF stopped loading new content. Then I opened a new tab and wrote about:memory and got the report. 

About addons, is there an easy way to report this? I have one disabled (disabled by FF), many plugins and three dictionaries.
Additional information to the attachement.

There was only one tab. It was the facebook News Feed. I scrolled down for eight minutes. Then FF stopped loading new content. Then I opened a new tab and wrote about:memory and got the report. 

About addons, is there an easy way to report this? I have one extension (disabled by FF), many plugins and three dictionaries.
Thanks for the memory report. The explicit allocations of Firefox itself (the things under explicit) look reasonable to me for both main process and content process (126MB and 253MB).

The main process has this, which also looks more or less reasonable:
2,047.94 MB (100.0%) -- address-space
├──1,274.18 MB (62.22%) ── free(segments=759)
├────466.81 MB (22.79%) ++ commit
└────306.95 MB (14.99%) -- reserved

However, the content process has this:

2,047.94 MB (100.0%) -- address-space
├──1,520.21 MB (74.23%) -- commit
│  ├──1,269.02 MB (61.97%) -- private
│  │  ├──1,257.54 MB (61.41%) ── readwrite(segments=1974)
│  │  └─────11.48 MB (00.56%) ++ (5 tiny)
│  ├────150.91 MB (07.37%) ++ mapped
│  └────100.28 MB (04.90%) ++ image
├────320.84 MB (15.67%) ++ reserved
└────206.89 MB (10.10%) ── free(segments=1096)

Some other large values measured in the content process:
1,273.93 MB ── private
1,089.27 MB ── resident
1,053.92 MB ── resident-unique
  947.28 MB ── system-heap-allocated
1,840.54 MB ── vsize
   11.81 MB ── vsize-max-contiguous

vsize-max-contiguous is really small, which means the process is in danger of failing to allocate a big block of memory.

So, the question is, what exactly is allocating all of that memory? Oftentimes, large hidden allocations like this are due to the graphics drive storing textures in the process. What does your about:support say? Does it get any better if you restart in safe mode (which should disable hardware acceleration)?
(In reply to Jorge Velasco from comment #4)
> About addons, is there an easy way to report this? I have one extension
> (disabled by FF), many plugins and three dictionaries.

That will be included in about:support, along with graphics driver information. If you could paste the contents of your about:support into a file and attach it to this bug that would be good. Thanks.
Summary: High memory usage in Firefox 52 when scrolling in Facebook → High system-heap-allocated memory usage in Firefox 52 when scrolling in Facebook
A user in bug 1300724 reported a somewhat similar issue that they were able to fix by updating their graphics driver.
See Also: → 1300724
Attached file file.txt
I got this file going to about:summary and clicking on "copy text to clipboard", then I paste it in a txt file.

You talked about disabling hardware acceleration. I disabled this option in FF long time ago. It was disabled during the test. I found this option under Options/Advanced/"Use hardware acceleration when available".

Anyway, I'll try to start in the safe mode.
(In reply to Jorge Velasco from comment #8)
> Created attachment 8847655 [details]
> file.txt
> 
> I got this file going to about:summary and clicking on "copy text to
> clipboard", then I paste it in a txt file.
> 
> You talked about disabling hardware acceleration. I disabled this option in
> FF long time ago. It was disabled during the test. I found this option under
> Options/Advanced/"Use hardware acceleration when available".
> 
> Anyway, I'll try to start in the safe mode.

Sorry, I meant "about:support", not "about:summary". :-)
Component: Untriaged → Graphics
Product: Firefox → Core
Attached file memory-report2.json.gz
I updated the NVIDIA driver, I restarted the PC and I opened FF in safe mode. I opened one single tab (Facebook News Feed). I scrolled down repeteadly until FF stopped loading content (it was 7 minutes). Then I got a new memory report and a new "about:support" report.

The memory report is attached to this message. Thanks.
Attached file file2.txt
Here you are, the updated "about:support" report.
Thanks for trying that out, though the new report looks the same as the old one.
Attached file memory-report3.json.gz
I attach a third memory repport, now for another PC, that with Windows 10 (32 bit) where I managed FF 52.0 (32 bit) to stop loading content to Facebook News Feed. It was in the Safe Mode and with Hardware Acceleration Enabled. I had only one tab and it was about half an hour when I started to have problems, scrolling down.
Attached file file3.txt
This is the "about:support" repport for the PC with Windows 10 mentioned in the last comment.
platform-rel: --- → ?
Whiteboard: [MemShrink] → [MemShrink][platform-rel-Facebook]
Whiteboard: [MemShrink][platform-rel-Facebook] → [MemShrink:P2][platform-rel-Facebook]
platform-rel: ? → -
Priority: -- → P3
Whiteboard: [MemShrink:P2][platform-rel-Facebook] → [MemShrink:P2][platform-rel-Facebook][gfx-noted]
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(jorgevelascobcn)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: