Bug 499800 - Memory leak when switching wallpapers on wayland
Summary: Memory leak when switching wallpapers on wayland
Status: RESOLVED DUPLICATE of bug 480693
Alias: None
Product: plasmashell
Classification: Plasma
Component: Image & Slideshow wallpaper plugins (other bugs)
Version First Reported In: 6.2.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-11 06:33 UTC by tcaptainpancake
Modified: 2025-02-12 16:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tcaptainpancake 2025-02-11 06:33:39 UTC
SUMMARY


STEPS TO REPRODUCE
1. launch a wayland session
2. Set wallpaper to slideshow or manually switch wallpapers 

OBSERVED RESULT
Memory usage starts to climb eventually leading to a crash I will provide a report next time I get the chance as it's not a quick crash from what I've seen

EXPECTED RESULT
No crash when using the feature

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
I am using an nvidia gpu and tried on both the arch and zen kernels
Comment 1 tcaptainpancake 2025-02-11 20:27:48 UTC
I may have reported this late or it was a different application because it seems to be working itself out now saw it get up to 2.6gb then drop back down to 362mb which seems perfect for my 32gb system I'll close this now!
Comment 2 tcaptainpancake 2025-02-11 20:29:18 UTC
Did not know you needed to close with a comment use to github lol
Comment 3 tcaptainpancake 2025-02-12 02:10:00 UTC
I guess I did not wait long enough as now it is up to 6.5gb ill post the crash log when it happens
Comment 4 TraceyC 2025-02-12 16:28:38 UTC
Thank you for the bug report! This looks to be the same issue as Bug 480693.

I'm marking this as a duplicate of that one, since the other has developer involvement. You can follow the progress of this issue in the other report.

*** This bug has been marked as a duplicate of bug 480693 ***
Comment 5 tcaptainpancake 2025-02-12 16:45:10 UTC
Sorry about that somehow missed it