[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #12 from Antonio Orefice--- For what is worth, the bug is present even in plasmoidviewer. Just play with it and see how his memory usage grows with ease. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #11 from Antonio Orefice--- I made a 3 minute run of that xdotool script (open and close wallpaper settings multiple times). Nvidia proprietary driver + QSG_RENDER_LOOP=basic Start: 286MB End: 486MB Nvidia proprietary driver + unset QSG_RENDER_LOOP Start: 281MB End: 533MB Nouveau + unset QSG_RENDER_LOOP Start 289MB End 436MB So, in the end it seems that NVIDIA blob is using more ram, but not that much, and plasma/qt are leaking more memory just because qt uses threads with nvidia proprietary driver, right? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #10 from David Edmundson--- please also try with QSG_RENDER_LOOP=basic plasmashell and report on what that does -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #9 from David Edmundson--- Oh, then it's not the issue that I fixed in 5.26 which was purely related to thumbnails. The wallpaper dialog doesn't do any custom GL, so if that's leaking only on NVidia it strongly implies the problem is higher in the stack than Plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #8 from Antonio Orefice--- Since it seems nouveau is not affected, I reported the very same to nvidia https://devtalk.nvidia.com/default/topic/966824/linux/huge-memory-allocation-on-plasmashell-with-proprietary-driver-nouveau-is-fine/post/4981667/?offset=5#4981701 In there, at posted a script using xdotool that did nothing else that showing the plasma configuration window; then the get wallpapers window, close both and reiterate. After 20 minutes of that, my system started swapping badly and plasma was eating almost 6GB of ram. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #7 from Antonio Orefice--- New info: with raster backend, apart from having a broken desktop, it seems plasma still allows me to interact with panels, so i interacted with them by using the menu, popup some tooltips, showed the calendar and so on. Well, with export QMLSCENE_DEVICE=softwarecontext i've a ram usage that starts with 228MB and ends to 276MB Using classic opengl, doing the exact same things, it starts at 228MB and reaches 420MB. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 Antonio Oreficechanged: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #6 from Antonio Orefice --- @David Edmundson : Are you able to reproduce with Nvidia proprietary drivers? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #5 from Antonio Orefice--- First time i tried was with framework 5.25. It persists with 5.26 qt5 is 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from David Edmundson --- What version of plasma-framework? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #3 from Antonio Orefice--- I forgot to add that running a compositor or not running a compositor makes 0 difference -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #2 from Antonio Orefice--- I just played with nuoveau, and found that it consumes so much less memory. With a quick test (show kickoff menu, clock, panel configuration window, moving a plasmoid): nvidia blob reached 400MB nuoveau stayed at about 250MB tried nvidia 367.35 and 370.28 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 Antonio Oreficechanged: What|Removed |Added Summary|plasmashell keeps eating|plasmashell keeps eating |ram, but never release it. |ram (NVIDIA BLOB), but ||never release it. -- You are receiving this mail because: You are watching all bug changes.