1627453 - Layers hardware acceleration causing high memory consumption on theguardian.com

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect, P3)

Description

[therube]

URL: https://www.theguardian.com/world/ng-interactive/2020/apr/03/coronavirus-map-of-the-us-latest-cases-state-by-state

Win7 x64
i5-3570k
16 GB RAM
Intel(R) HD Graphics 4000, driver 10.18.10.4885

FF 76.0a1, 20200403214010

layers.acceleration.disabled;false

Result:

Both FF & 'NT Kernel & System' CPU usage went through the roof, bringing my system to a virtual standstill.

Had to kill FF.
And then it still took ~1 minute (after FF quit) before 'NT Kernal & System' CPU usage finally resided.

Setting, layers.acceleration.disabled;true does help.

With that, while there is still high CPU usage, that usage is "sandboxed" within firefox.exe itself, 'NT Kernal & System' is not negatively affect. Likewise, my computer system remains responsive.

Similar to, Bug 1606162 Playing video on Videobin.co results in high CPU - in ntoskrnl.exe, Windows 7.

This is the crash report (I guess from my kill, or at least from its' shutdown), https://crash-stats.mozilla.org/report/index/93742e5f-218f-421a-b767-bff820200404.

Comment 1

[therube]

Attachment: about:support

Comment 2

[therube]

Attachment: about:support

Comment 3

[therube]

No change in behavior after updating to the latest Intel drivers, video driver version 10.18.10.5129.

Comment 4

[Mayank Bansal]

I can confirm the high memory use if I disable WR, and use advanced layers.
I am on HD 5500, with the latest drivers

Comment 5

[Mayank Bansal]

Attachment: memory-report.json.gz

hopefully this captures the high memory use

Comment 6

[Jessie [:jbonisteel] pls NI]

Sotaro, curious if you can repro on Win10?

Comment 7

[Alice0775 White]

gfx.content.azure.backends = skia will fix the memory issue.

Comment 8

[Sotaro Ikeda [:sotaro]]

(In reply to Jessie [:jbonisteel] pls NI from comment #6)

Sotaro, curious if you can repro on Win10?

Yes, I can reproduce it on Win10. It seems to caused by d2d usage and pref gfx.content.azure.backends=skia addressed the problem.

D2D usage sometimes caused huge memory problems like Bug 1432086.

Comment 9

[Denis Palmeiro [:denispal]]

Reproducible for me as well on windows 10 with d3d-al. Here is a profile https://perfht.ml/3cjFFiO.
Marking as qf:p1 since it basically goes OOM and ends up crashinig my computer, and it's also an article on covid-19 which is likely popular right now.

Comment 10

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Comment 11

[Bas Schouten (:bas.schouten)]

This has been fixed now that we have webrender.