Bug 509788

Summary:	Gifs used as wallpaper cause vram leaking
Product:	[Plasma] plasmashell	Reporter:	socket772
Component:	Image & Slideshow wallpaper plugins	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kdedev, notmart, qydwhotmail
Priority:	NOR
Version First Reported In:	6.4.5
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Attached gif is the one that i used

Description socket772 2025-09-22 16:33:10 UTC

Created attachment 185155 [details]
Attached gif is the one that i used

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
When using a gif as wallpaper causes vram usage increase until system goes into a out of memory state. This happens 100% of the times on my system. Didn't notice this behavior if gif is used as lock screen

STEPS TO REPRODUCE
1. Add gif as wallpaper
2. Select and apply gif as active wallpaper

OBSERVED RESULT
The vram usage increases until system crashes

EXPECTED RESULT
The vram usage should not increase infinitely until system crash

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux x86_64 (Linux 6.16.8-arch2-1)
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION
WM: KWin (Wayland)
WM Theme: Breeze
CPU: AMD Ryzen 7 9700X (16) @ 5.58 GHz
GPU: NVIDIA GeForce RTX 2060 SUPER [Discrete]
Memory: 30.94 GiB
Swap: 27.74 GiB
Locale: en_US.UTF-8

Comment 1 socket772 2025-09-22 16:41:51 UTC

Small addendum. You don't even need to apply the change, the gif just needs to be active in the wallpaper

Comment 2 TraceyC 2025-09-22 16:59:45 UTC

Thank you for the bug report! This looks to be the same issue as Bug 483602.

I'm merging this request into that one. You can follow the progress of this issue in the other report.

*** This bug has been marked as a duplicate of bug 483602 ***