Closed Bug 2053263 Opened 1 month ago Closed 1 month ago

[HDR/Windows] Memory leak when playing HDR video

Categories

(Core :: Graphics: Color Management, defect, P2)

Firefox 153
Desktop
Windows
defect

Tracking

()

RESOLVED FIXED
154 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr140 --- unaffected
firefox152 --- unaffected
firefox153 + fixed
firefox154 + fixed

People

(Reporter: ahale, Assigned: ahale)

References

(Regression)

Details

(Keywords: regression)

Attachments

(2 files)

I did some about:memory comparisons to verify if there are any memory leaks with the new ShaderBlt code (Bug 2037689) and found some, we should fix these before shipping.

I'm marking this bug as S2 because:

  • it is a memory leak - ~200MiB GPU memory per HDR video
  • it is a regression (without ShaderBlt code we would not be showing HDR video though)
  • there is a plausible user story where something is visibly wrong - watching ~50 TV show episodes that are 4K@60hz HDR could result in 10GiB of GPU memory usage which might cause the GPU process to restart (causing a brief flash as the browser redraws everything) and affects the system negatively overall (other apps may become slower until the GPU process restarts).

An argument could be made for S3 because the user story isn't very common, and the recovery mechanism is completely automatic, and it also has reasonable workarounds (restarting the browser is one option, pressing the Trigger GPU Reset option in about:support is another, and turning off HDR desktop mode is another).

Keywords: regression
Regressed by: 2037689

Set release status flags based on info from the regressing bug 2037689

Attachment #9605530 - Flags: approval-mozilla-beta?

firefox-beta Uplift Approval Request

  • User impact if declined/Reason for urgency: A GPU memory leak occurs when viewing several HDR videos in a single session. Not fatal - GPU process should recover, but still not a good thing to do in terms of competing with other apps for system resources.
  • Code covered by automated testing?: no
  • Fix verified in Nightly?: yes
  • Needs manual QE testing?: no
  • Steps to reproduce for manual QE testing:
  • Risk associated with taking this patch: low
  • Explanation of risk level: Low because this refcounting approach is well understood and it is simply fixing a bug that led to excessive retention of resources.
  • String changes made/needed?: N/A
  • Is Android affected?: no
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 154 Branch
Attachment #9605530 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

This doesn't need QA testing, the fix has been verified manually and would not vary by computer.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: