1818982 - High memory used for gpu-committed and gpu-shared while on YouTube

Status: RESOLVED DUPLICATE of bug 1897006

(Core :: Audio/Video: Playback, defect, P3)

Description

[gidcheen]

Attachment: memory-report.json.gz

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

Steps to reproduce:

open any YouTube video. with my 12th gen intel and RTX 3060 laptop on Windows 11.

does not happen with my intel 8th gen + GTX 1060 laptop or my ryzen 3700 + RX 5700 desktop. Does not happen under linux (ubuntu KDE + Gnome) under any of those devices.

Actual results:

memory jumps from 600mb to 5-6gb after a 8-10 min video.
increases with every additional video.
memory only increases during video playback
about:memory doesnt seem to reflect that memory usage

Expected results:

stable memory usage like on my several other devices

Comment 1

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

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[gidcheen]

It seems to be GPU memory allocated by the intel iGPU and not CPU memory.

Comment 3

[gidcheen]

Does not happen with hardware acceleration disabled

Comment 4

[AliA88]

I am having a issue when I play a utube video and move the browser on my desktop left and right many times my 64gb ram fills up no other browser does this I have even memtest my ram and no issues what is Firefox doing been using Firefox for years this is insane, I have logged my issue as a bug here but no one has responded back, if I keep moving the browser on my desktop and let the ram fill up and once it's full and I keep doing it so it has zero ram left the pc bluescreens and has the exact same error code each time. Other browsers have no issues.

Comment 5

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

The severity field is not set for this bug.
:jimm, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 6

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

I've been going through your memory report. I see the gpu-shared and gpu-committed are particularly concerning in the GPU process:
4,552.59 MB ── gpu-committed
0.00 MB ── gpu-dedicated
4,614.07 MB ── gpu-shared
29.99 MB ── heap-allocated
1.00 MB ── heap-chunksize
53.00 MB ── heap-mapped
5,430.18 MB ── private
5,420.59 MB ── resident
5,366.33 MB ── resident-unique

This doesn't seem to be any explicit textures we are tracking:

137.79 MB (100.0%) -- gfx
└──137.79 MB (100.0%) -- webrender
├──131.07 MB (95.13%) -- textures
│ ├───40.00 MB (29.03%) ── render-targets
│ ├───37.64 MB (27.32%) -- texture-cache
│ │ ├──37.00 MB (26.85%) ── atlas
│ │ └───0.64 MB (00.47%) ── standalone
│ ├───34.34 MB (24.92%) ── swap-chains
│ ├───13.78 MB (10.00%) ── render-texture-hosts
│ ├────3.25 MB (02.36%) ── upload-staging-textures
│ └────2.06 MB (01.50%) ++ (5 tiny)
└────6.71 MB (04.87%) -- images/mapped_from_owner
├──6.64 MB (04.82%) -- pid=6308
│ ├──4.88 MB (03.54%) ── image(800x800, compositor_ref:2, creator_ref:1)/decoded-nonheap [2]
│ └──1.76 MB (01.28%) ++ (35 tiny)
└──0.07 MB (00.05%) ++ (7 tiny)

Which suggests maybe there is a memory leak in the driver code?

Could you attach your about:support and see if there are newer drivers available on Windows?

Comment 7

[AliA88]

(In reply to Andrew Osmond [:aosmond] (he/him) from comment #6)

I've been going through your memory report. I see the gpu-shared and gpu-committed are particularly concerning in the GPU process:
4,552.59 MB ── gpu-committed
0.00 MB ── gpu-dedicated
4,614.07 MB ── gpu-shared
29.99 MB ── heap-allocated
1.00 MB ── heap-chunksize
53.00 MB ── heap-mapped
5,430.18 MB ── private
5,420.59 MB ── resident
5,366.33 MB ── resident-unique

This doesn't seem to be any explicit textures we are tracking:

137.79 MB (100.0%) -- gfx
└──137.79 MB (100.0%) -- webrender
├──131.07 MB (95.13%) -- textures
│ ├───40.00 MB (29.03%) ── render-targets
│ ├───37.64 MB (27.32%) -- texture-cache
│ │ ├──37.00 MB (26.85%) ── atlas
│ │ └───0.64 MB (00.47%) ── standalone
│ ├───34.34 MB (24.92%) ── swap-chains
│ ├───13.78 MB (10.00%) ── render-texture-hosts
│ ├────3.25 MB (02.36%) ── upload-staging-textures
│ └────2.06 MB (01.50%) ++ (5 tiny)
└────6.71 MB (04.87%) -- images/mapped_from_owner
├──6.64 MB (04.82%) -- pid=6308
│ ├──4.88 MB (03.54%) ── image(800x800, compositor_ref:2, creator_ref:1)/decoded-nonheap [2]
│ └──1.76 MB (01.28%) ++ (35 tiny)
└──0.07 MB (00.05%) ++ (7 tiny)

Which suggests maybe there is a memory leak in the driver code?

Could you attach your about:support and see if there are newer drivers available on Windows?

This could explain why there is no issue when there is no display driver installed or when I use a very old display driver I can't replicate the issue and I was thinking it's the audio driver, sure I will post what u ask for, but I can't install the latest Nvidia driver since it's been confirmed to have issues on certain machines and I am avoiding that driver due these issues presented and confirmed by Nvidia. I am using the driver 531.18 but there is a one newer version then this which has lots of issues at the moment and I haven't installed because of the problems it brings. But one thing is confusing me other browsers have no issues regarding this it's only Firefox. Thanks for the update

Comment 8

[AliA88]

(In reply to Andrew Osmond [:aosmond] (he/him) from comment #6)

I've been going through your memory report. I see the gpu-shared and gpu-committed are particularly concerning in the GPU process:
4,552.59 MB ── gpu-committed
0.00 MB ── gpu-dedicated
4,614.07 MB ── gpu-shared
29.99 MB ── heap-allocated
1.00 MB ── heap-chunksize
53.00 MB ── heap-mapped
5,430.18 MB ── private
5,420.59 MB ── resident
5,366.33 MB ── resident-unique

This doesn't seem to be any explicit textures we are tracking:

137.79 MB (100.0%) -- gfx
└──137.79 MB (100.0%) -- webrender
├──131.07 MB (95.13%) -- textures
│ ├───40.00 MB (29.03%) ── render-targets
│ ├───37.64 MB (27.32%) -- texture-cache
│ │ ├──37.00 MB (26.85%) ── atlas
│ │ └───0.64 MB (00.47%) ── standalone
│ ├───34.34 MB (24.92%) ── swap-chains
│ ├───13.78 MB (10.00%) ── render-texture-hosts
│ ├────3.25 MB (02.36%) ── upload-staging-textures
│ └────2.06 MB (01.50%) ++ (5 tiny)
└────6.71 MB (04.87%) -- images/mapped_from_owner
├──6.64 MB (04.82%) -- pid=6308
│ ├──4.88 MB (03.54%) ── image(800x800, compositor_ref:2, creator_ref:1)/decoded-nonheap [2]
│ └──1.76 MB (01.28%) ++ (35 tiny)
└──0.07 MB (00.05%) ++ (7 tiny)

Which suggests maybe there is a memory leak in the driver code?

Could you attach your about:support and see if there are newer drivers available on Windows?

Sorry wrong reply thought u replied to my bug which is same issue.

Comment 9

[homa-jo]

I can reproduce this Bug and have an alowed adress space of 134 TB, at the moment, Taskmanager says 8GB used.
AMD newest driver.
With d4planner.io and www.wetteronline.de/wetterradar I can easily reproduce it.
Other Measurements

134,217,727.94 MB (100.0%) -- address-space
├──132,111,960.36 MB (98.43%) ── free(segments=736)
├────2,103,369.61 MB (01.57%) -- reserved
│ ├──2,097,119.87 MB (01.56%) ── mapped(segments=15)
│ └──────6,249.74 MB (00.00%) ── private(segments=571)
└────────2,397.97 MB (00.00%) -- commit
├──1,762.59 MB (00.00%) ++ private
├────359.07 MB (00.00%) ++ image
└────276.31 MB (00.00%) ++ mapped

Should I open an new bug report?

Comment 10

[Andrew McCreight [:mccr8]]

Yes, please file a new bug.

Comment 11

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

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit BugBot documentation.

Comment 12

[stevenwdv]

Hi! I too have this bug. The Windows Resource-Exhaustion-Detector is killing random other processes on my PC while I have Firefox open in the background with just a single YouTube tab playing, which is really annoying. The Firefox GPU process is using 37 GB of virtual memory (I have just 16 GB of actual RAM, so it's reserving a lot of swap as well). Note that, accoding to System Informer (formerly Process Hacker), the Working set is just 176 MB (I think this may mean that the amount of physical memory usage is lower, but that Windows is still reserving the memory in case Firefox does end up using it).

about:memory gives the following summary about the GPU process:

         47.76 MB ── d3d11-shared-textures
          0.00 MB ── gfx-d2d-vram-draw-target
          0.01 MB ── gfx-d2d-vram-source-surface
     37,800.17 MB ── gpu-committed
        554.20 MB ── gpu-dedicated
         38.42 MB ── gpu-shared
         68.91 MB ── heap-allocated
          1.00 MB ── heap-chunksize
     38,099.61 MB ── private
        181.02 MB ── resident
        115.24 MB ── resident-unique
          4.08 MB ── shmem-allocated
         50.31 MB ── shmem-mapped
         43.63 MB ── system-heap-allocated
                0 ── unresolved-ipc-responses
  2,142,877.99 MB ── vsize
129,671,492.86 MB ── vsize-max-contiguous
                0 ── webgl-buffer-count
          0.00 MB ── webgl-buffer-memory
                0 ── webgl-context-count
                0 ── webgl-renderbuffer-count
          0.00 MB ── webgl-renderbuffer-memory
                0 ── webgl-shader-count
                0 ── webgl-texture-count
          0.00 MB ── webgl-texture-memory

If there is anything I can do to diagnose this bug, please let me know!

Comment 13

[stevenwdv]

By the way, I have an AMD Radeon RX 7800 XT GPU.

Comment 14

[xse]

Firefox 126.0 (Build ID 20240509170740) mozilla-MSIX Windows 11
AMD Ryzen 7 PRO 6850U with Radeon Graphics

Firefox open for a while, browsing, watching videos when computer goes

"You're running low on disk space"

gpu process sitting at over 20GB reserved memory -> about:memory screenshot