VRAM leak through Firefox?

Question

Video cards

Recently discovered that Firefox consumes some inadequate amount of video memory - I even wanted to issue a question about this, but postponed it. Literally an hour ago, dwm.exe crashed - presumably due to the fact that VRAM was no longer enough (or RAM + pagefile, where, in my opinion, excess data from VRAM is swapped).

Here is the picture I have now in the task manager

This was the last time

Under the GPU and RAM tabs .
At first, I didn’t believe in 17 gigabytes either - I had to double-check.

Errors from Event Viewer

Всплывающее окно приложения: Windows - Нехватка виртуальной памяти : Свободная виртуальная память системы заканчивается. Чтобы обеспечить нормальную работы Windows, увеличьте размер файла подкачки виртуальной памяти. Дополнительные сведения содержатся во встроенной справке.
Нехватка виртуальной памяти в системе успешно обнаружена. Наибольший объем виртуальной памяти был выделен следующим программам: для ffmpeg.exe (13668) выделено 2822156288 байт, для firefox.exe (14344) выделено 1074171904 байт и для dwm.exe (1536) выделено 966758400 байт.
После чего DWM успешно грохнулся и перезапустился.

So, in fact, the question is: how to check if there is a memory leak problem? Including inside the browser? I dug into a wide variety of about:... but there is only information on memory consumption (or I did not find a GPU).
Who is to blame and what to do?
UP:
To clarify, I found a GPU in about:memory, but it does not recognize where 4+ giga of video memory is.

GPU (pid 14524)

Explicit Allocations
4.98 MB (100.0%) -- explicit
├──3.44 MB (68.95%) ── heap-unclassified
├──1.12 MB (22.55%) -- heap-overhead
│ ├──0.58 MB (11.60%) ── page-cache
│ ├──0.47 MB (09.40%) ── bin-unused
│ └──0.08 MB (01.55%) ── bookkeeping
├──0.15 MB (02.98%) ── telemetry
├──0.14 MB (02.76%) -- xpcom
│ ├──0.13 MB (02.54%) ── component-manager
│ └──0.01 MB (00.21%) ── category-manager
├──0.14 MB (02.74%) -- atoms
│ ├──0.14 MB (02.74%) ── table
│ └──0.00 MB (00.00%) ── dynamic-objects-and-chars
└──0.00 MB (00.02%) ── profiler/profiler-state
Other Measurements
134,217,727.94 MB (100.0%) -- address-space
├──132,114,937.90 MB (98.43%) ── free(segments=180)
├────2,101,664.39 MB (01.57%) -- reserved
│ ├──2,097,130.29 MB (01.56%) ── mapped(segments=13)
│ └──────4,534.10 MB (00.00%) ── private(segments=253)
└────────1,125.65 MB (00.00%) ++ commit
4.98 MB (100.0%) -- heap-committed
├──3.86 MB (77.45%) ── allocated
└──1.12 MB (22.55%) ── overhead
12 (100.0%) -- observer-service
└──12 (100.0%) -- referent
├──11 (91.67%) ── strong
└───1 (08.33%) -- weak
├──1 (08.33%) ── alive
└──0 (00.00%) ── dead
0.02 MB ── gfx-surface-win32
3.86 MB ── heap-allocated
1.00 MB ── heap-chunksize
6.00 MB ── heap-mapped
720.89 MB ── private
331.38 MB ── resident
217.29 MB ── resident-unique
21.67 MB ── system-heap-allocated
2,102,790.04 MB ── vsize
130,272,180.56 MB ── vsize-max-contiguous
End of GPU (pid 14524)

Unless, of course, the task manager is cheating. However, he is hardly deceiving, because AIDA also says that 9+ gigabytes have been used right now. I'm not one of those who is shaking over every megabyte of memory, but at the same time it seems to me that VRAM should not fly into one browser like that.

Answer 1

In general, updating Firefox solved the problem apparently.
And yes - do not trust the task manager.

Answer 2

1 - how about looking for viruses?
2 - if the profile (or several) of firefox survived the upgrade to quantum, or more radical updates of fox - it is worth clearing the profile (profiles) even without suspicion of malware / miners. just clean it up so it doesn't bug. the list of the most valuable files is here - https://support.mozilla.org/ru/kb/profili-gde-fire...
my choice of files to save:

content-prefs.sqlite
favicons.sqlite
key4.db
logins.json
permissions.sqlite
places.sqlite
sessionstore.jsonlz4