Summary: | Memory leak only on Wayland | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Jaime Antonio Gonzalez <enigma1052666> |
Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | nate |
Priority: | NOR | Keywords: | wayland-only |
Version First Reported In: | master | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | unresolved functions tree |
Description
Jaime Antonio Gonzalez
2025-06-26 06:01:58 UTC
Do you use a slideshow wallpaper? If so, this is Bug 480693, which was traced to an issue in the NVIDIA driver. Frankly, the issue you're seeing is almost certainly also an issue in the NVIDIA driver even if it's not that exact issue. Thanks for the debugging you've done to make that clear! It's very helpful. (In reply to Nate Graham from comment #1) > Do you use a slideshow wallpaper? If so, this is Bug 480693, which was > traced to an issue in the NVIDIA driver. > > Frankly, the issue you're seeing is almost certainly also an issue in the > NVIDIA driver even if it's not that exact issue. Thanks for the debugging > you've done to make that clear! It's very helpful. Yes, I'm using the slideshow wallpaper. I just tried with a static image and it leaks but not that crazy (around 160 MiB) I tried slideshow only on monitor 2 (driven by the HD2000 IGP) it leaks a bit higher than no slideshow (around 175 MiB) I tried slideshow only on monitor 1 (driven by the GTX1060) it leaks almost the same as slideshow only on monitor 2 But using slideshow on the 2 monitors, makes it leak big again. I have set the timer to switch images to 1 min. Strangely, after killing and restarting plasmashell 3 or 4 times, it behaves correctly. Thanks, it's Bug 480693 then. Any remaining leaks when *not* using a slideshow wallpaper are very likely to also be NVIDIA driver issues too. *** This bug has been marked as a duplicate of bug 480693 *** |