texture cache leak (or endlessly rising memory usage) when doing Whereby calls
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: kairo, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
application/gzip
|
Details |
In the last days (didn't happen early last week but I had no Whereby calls then and Tuesday or so of this week), I've seen memory usage rise endlessly while doing Whereby.com calls (1:1 is enough) in Nightly on my laptop running Linux (openSUSE Tumbleweed) on NVidia gfx (using the proprietary driver) - but not sure if the setup is relevant other than me having WebRender enabled.
The memory usage goes up until all memory is full and all swap is full and makes the whole machine freeze - unless I either close Nightly early enough or go to about:memory and click "minimize memory usage", which seems to completely fix it.
When going into about:memory, basically all this memory is in gfx / webrender / textures / texture-cache which is why I'm guessing this to be a WebRender bug.
Interestingly, I so far could not reproduce by doing a Jitsi call or by watching YouTube, but when I have an active Whereby call with someone else, it always happens.
Reporter | ||
Updated•4 years ago
|
Comment 1•4 years ago
|
||
I think I am observing the same issue with Google Meet. I am using Nightly on MacOS. I can't reliably reproduce just yet.
Updated•4 years ago
|
Comment hidden (off-topic) |
Updated•4 years ago
|
Comment hidden (off-topic) |
Comment 4•4 years ago
|
||
Robert, can you get a new memory report with a Nightly with a build id of 20201215213427 or newer?
Reporter | ||
Comment 5•4 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #4)
Robert, can you get a new memory report with a Nightly with a build id of 20201215213427 or newer?
Was any change in that build that may fix this? I haven't run into this issue in recent builds, I think, though I had a few Whereby calls.
Updated•4 years ago
|
Description
•