1696827 - Video memory leak on any long(ish)-running <video>

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebRender, defect, P2)

Description

[Justin Peter]

Attachment: about:support after experiencing the issue

Over time I have noticed a slow leak of video memory on Youtube. I see it reproducibly when watching a playlist of videos at 3-4x speed (via extension). After 1-2 hours, Firefox will freeze for 1-2 minutes at ~7.5GB (shared) video memory, before finally releasing the memory and unfreezing. Opening about:memory appears to set off this process (freezing the browser) early. As a result, I do not (yet) have a good memory capture/dump. I'm not sure if opening about:memory before the leak occurs will allow me to take a capture; otherwise, I assume I should be able to do so using task manager. In either of these situations, I'm not sure whether there will be any sensitive information involved and (if so) what the best way to get that to whoever the relevant person is would be.

About:support while watching Youtube and after a freeze is attached. (Interestingly, it appears to say that webrender failed to initialize. I'll have to look more to see if that's a persistent issue/what it may be caused by.) About:support from a new session will be attached below.

Due to the amount of time required to reproduce this issue, I have not yet verified the issue in any of the following circumstances:

• Disabling fission
• Updating to the latest graphics driver (my version is only ~2 months old, and the stable version installed by Windows)

Comment 1

[Justin Peter]

Attachment: about:support from a new session

Comment 2

[Justin Peter]

Webrender appears to be starting normally, so it may be the case the the leak causes it to crash and fall back to another compositor.

Comment 3

[Justin Peter]

This occurs when playing any video, not just videos on youtube.

Comment 4

[Justin Peter]

Watching one long video straight through, this led to full video memory and a freeze after 35 minutes of playback. (In other circumstances, it has taken longer.) It now appears to fall back to software webrender (it was falling back to a different compositor previously), which does not exhibit the issue.

Comment 5

[Miko Mynttinen]

(In reply to Justin Peter from comment #4)

Watching one long video straight through, this led to full video memory and a freeze after 35 minutes of playback. (In other circumstances, it has taken longer.) It now appears to fall back to software webrender (it was falling back to a different compositor previously), which does not exhibit the issue.

Sorry for the late reply. Does this mean you are no longer experiencing this issue?

Comment 6

[Justin Peter]

Sorry, that wasn't quite clear. The issue still exists, but after webrender crashes and falls back to software webrender (previously it fell back to the basic compositor), I'm fairly certain that the issue will not pop up again in the same session.

If I get a process dump while it's in a leaky state, would that be of help?

Comment 7

[Justin Peter]

I did manage to get two dumps: one from Firefox (attached), which seems to have no information other than that there is a lot of VRAM being used. I also captured a process dump (via task manager) of the process using lots of memory. Thankfully, it compressed very well (to 2% of the original size), but that report is presumably not anonymized, so if you have a good slightly-more-private way to send that to you, hopefully it could be more informative.

If there's anything else I could do to help, please feel free to ask.

Comment 8

[Justin Peter]

Attachment: memory-report.json.gz

Comment 9

[Andrew Osmond [:aosmond] (he/him)]

gpu-committed is 3,336.96 MB and gpu-shared is 3,385.79 MB, that seems to be the biggest chunk, and it doesn't seem to be captured in our other reporting in the GPU process such as the texture host. This suggests either the reporting is missing stuff, or something inside Windows is holding onto that memory.

Comment 10

[Justin Peter]

Would a Windows process dump help?

The see also post is on MacOS so that may indicate that it's not a Windows-specific bug.

Comment 11

[Andrew Osmond [:aosmond] (he/him)]

Yes, I will contact you with a link where you can share the process dump, thanks.

Comment 12

[Justin Peter]

I have not experienced this for several months.

I don't know if this was due to an update in Windows, Firefox, or my graphics driver. (The process dump may point to the root cause; I have no idea.)

Comment 13

[BugBot [:suhaib / :marco/ :calixte]]

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Comment 14

[Deandre]

Did your bug fix or not? I'm also facing such issue from the day one. Do you know about this: https://apkfelx.com/dead-trigger-2-mod-apk/

Comment 15

[John Williams]

In today’s digital and technological era, websites are essential elements for establishing and elevating your corporate business identity, No organization can sustain and rise without having a strong physical website presence, The process of creating a website can be accomplished by hiring a custom software developer.
https://erstech.org/

Comment 16

[Firefox User]

Do you still experience this issue?

Comment 17

[Justin Peter]

No, I haven't experienced this for at least a year and a half.