Closed Bug 1763370 Opened 4 years ago Closed 4 years ago

Accelerated canvas enabled on https://www.mtjo.net/ memory increased to 100%

Categories

(Core :: Graphics: Canvas2D, defect)

Firefox 100
defect

Tracking

()

RESOLVED FIXED
102 Branch
Tracking Status
firefox102 --- fixed

People

(Reporter: 894846254, Assigned: lsalzman)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

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

Steps to reproduce:

Set gfx.canvas.accelerated to true
Visit https://www.mtjo.net

performance profile: https://share.firefox.dev/3DK6Ods

Actual results:

The memory gradually increases to 100% after a few seconds of visiting the webpage

Attached image task manager.png

The Bugbug bot thinks this bug should belong to the 'Core::Canvas: 2D' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Canvas: 2D
Product: Firefox → Core
Blocks: gpu-canvas
Severity: -- → S3
Status: UNCONFIRMED → NEW
Ever confirmed: true

It seems that client WebGL textures get GC'd way later than is really useful,
so we need to ensure that we explicitly delete WebGL textures to ensure that
it happens in a timely fashion.

Assignee: nobody → lsalzman
Status: NEW → ASSIGNED
Pushed by lsalzman@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e41ee66c5b9b Explicitly delete WebGL textures in DrawTargetWebgl. r=aosmond,gfx-reviewers
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
QA Whiteboard: [qa-102b-p2]

Hello there! I tried to reproduce this issue on Firefox 100.0, Win10 x64 bits, but the URL provided by the reporter is unresponsive. Instead I reproduced the memory usage issue using this link (link provided from a dupe of this bug). Memory increase up to 90% in Task Manager.
I verified the fixes in Firefox 102.0b5(20220607212916) and Nightly 103.0a1(20220608214824) on Win10 x64 and the memory drops significantly - around 50% maximum.
Given the fact that memory usage dropped by about half, I assume this would be the expected behavior of the fix?
Thank you.

Flags: needinfo?(lsalzman)
Regressions: 1781798
Flags: needinfo?(lsalzman)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: