Closed Bug 1532749 Opened 5 years ago Closed 3 years ago

[Direct3D 11 (Advanced Layers)] Loading a website causes an insane spike in RAM (15GB) even with a clean profile, when it works fine on other browsers

Categories

(Core :: Graphics: Layers, defect, P3)

Product:
Core
Component:
Graphics: Layers
Version:
65 Branch
Platform:
Unspecified
Windows
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Project Flags:
Performance Impact medium
Tracking Flags:
Tracking Status
firefox-esr60 --- wontfix
firefox-esr78 --- wontfix
firefox65 --- wontfix
firefox66 --- wontfix
firefox67 --- wontfix
firefox68 --- wontfix

People

(Reporter: justanotherguy3571, Unassigned)

References

Details

(5 keywords)

Attachments

(1 file)

Task manager loaded with a clean profile attempting to load the site
(deleted), image/png
Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

Go to http://notabilia.net, and watch the RAM usage hit 15gb on a clean profile, or >32gb on an existing heavier profile.

Actual results:

I noticed that website was freezing up my PC when attempting to load. I checked my RAM and all 32gb had been eaten up. I made a clean profile to check it works before figuring out which extension was causing it, and was pretty surprised to see the spike happen in a completely fresh profile too.
The usage was less with a clean profile but still extremely high

Expected results:

Website loads without burning all your RAM.

Keywords: memory-footprint

I could reproduce this issue on

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Component: Untriaged → DOM
Product: Firefox → Core
Status: UNCONFIRMED → NEW
status-firefox65: --- → wontfix
status-firefox66: --- → wontfix
status-firefox67: --- → affected
status-firefox-esr60: --- → wontfix
Ever confirmed: true
Keywords: regression

So far I haven't reproduced on Nightly/Linux.

On Nightly67.0a1 Window10,
it works if WebRender enabled.
It works if HWA disabled.

But, the problem is reproduced if HWA(Direct2D) enabled.

Component: DOM → Graphics
OS: Unspecified → Windows
Summary: Loading a website causes an insane spike in RAM (15GB) even with a clean profile, when it works fine on other browsers → [Direct2D] Loading a website causes an insane spike in RAM (15GB) even with a clean profile, when it works fine on other browsers
Component: Graphics → Graphics: Layers
Summary: [Direct2D] Loading a website causes an insane spike in RAM (15GB) even with a clean profile, when it works fine on other browsers → [Direct3D 11 (Advanced Layers)] Loading a website causes an insane spike in RAM (15GB) even with a clean profile, when it works fine on other browsers

There are at least 2 regressions.

#1 regression: Browser hang up, but memory usage is small.
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=25d4e570f1d983ecc112e835d8a23eeafa8cd684&tochange=a9ec5effe35f607793514fe3688efb3ba8096689

Regressed by: Bug 1248913

#2 regression: Browser and Windows hang up, and memory usage is full.
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=81ea83beadf846f0d8f691162e5ef74cddf3c47a&tochange=13fe99de32f645984008a2ddc31923093a9fa43a

Regressed by: 13fe99de32f6 Bas Schouten — Bug 1300338: Do not attempt to preserve layer content when we're going to override it in a blend operation anyway. r=jrmuizel

Blocks: 1248913, 1300338
Has Regression Range: --- → yes
Has STR: --- → yes

This could be qf or memshrink, but rather bad anyhow.

Whiteboard: [qf]
Whiteboard: [qf] → [qf:p2:resource]

Hey Bas, could you help take a look at this one? Thanks!

Flags: needinfo?(bas)
Priority: -- → P3

Marking as fix-optional for 67 as this is a long standing issue and the bug is unassigned. If an safe patch materializes, we can evaluate uplifting it.

status-firefox67: affected → fix-optional
status-firefox68: --- → affected

Bulk change to wontfix for 68 (P3+ carryover with needinfo).

status-firefox68: affected → wontfix

We shouldn't be using this anymore with WR.

Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(bas)
Resolution: --- → FIXED
Performance Impact: --- → P2
Keywords: perf:resource-use
Whiteboard: [qf:p2:resource]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: