https://bugs.kde.org/show_bug.cgi?id=464582
Bug ID: 464582
Summary: NVIDIA completely freezing applications & desktop
itself when VRAM is close to being filled
Classification: Plasma
Product: kwin
Version: 5.26.90
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: kodatar...@yahoo.com
Target Milestone: ---
SUMMARY
***
Whenever the VRAM is close to being full(example: you are playing a high
demanding title which almost always uses 99% of the VRAM 7955MB out of 8192MB)
other applications like discord/spotify/web browser(firefox/chromium/chrome)
would just completely hang, frozen window until you close and re-open it again.
At least on NVIDIA gpu.
***
STEPS TO REPRODUCE
1. Play a very demanding title which almost always goes on to fill your
VRAM(Ready Or Not comes to mind), where it stays 99% being filled and have
discord/web browser or any client in general opened on your second monitor or
in the background.
OBSERVED RESULT
The application has completely frozen.
EXPECTED RESULT
To work just fine without freezing as on other desktop environments(tested
Gnome, Cinnamon and Mate).
SOFTWARE/OS VERSIONS
Operating System: EndeavourOS
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.7-273-tkg-pds (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2
ADDITIONAL INFORMATION
Just wanted to write down that this bug is observed under both X11 and Wayland,
with wayland making the entire session unresponsive until you close out the
game/app which consumes so much VRAM.
In addition this seems to happen only with NVIDIA, as I am unable to reproduce
it with AMD card.
It has been happening for quite sometime now, which I thought it was an issue
that the VRAM can't take it, however after trying other Desktop Environments it
seems the problem lies with KDE Plasma(X11/Wayland).
NOTE: This issue isn't limited to 5.26.90, I am only reporting it just now, but
it has been present in all versions, so it isn't a 5.27 Beta bug.
--
You are receiving this mail because:
You are watching all bug changes.
