Bug 477229

Summary: Huge memory consumption when playing certain gifs
Product: [Plasma] plasmashell Reporter: Kloud <kde>
Component: Splash ScreensAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: kde, nate
Priority: NOR    
Version First Reported In: 6.0.3   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Heaptrack trace of ksplashqml and the splashscreen itself

Description Kloud 2023-11-19 13:07:33 UTC
Created attachment 163289 [details]
Heaptrack trace of ksplashqml and the splashscreen itself

SUMMARY
***
Playing certain splashscreens causes ksplashqml to consume a lot of RAM
I am attaching the splashscreen and heaptrack trace 
***


STEPS TO REPRODUCE
1. Install the splash
2. Start the splash (ksplashqml Overload --test)


OBSERVED RESULT
ksplashqml consumes 5Gb of RAM

EXPECTED RESULT
ksplashqml does not consume as much RAM

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version:  5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
Comment 1 Kloud 2024-04-07 10:28:14 UTC
Same thing happens after updating to plasma 6 (6.0.3)
Comment 2 Nate Graham 2025-04-29 16:27:48 UTC
Sorry we weren't able to get to this bug report yet. Are any of these issues still happening in Plasma 6.3.4 or later?

Also, what kind of GPU hardware are you using?

Thanks a lot!
Comment 3 Bug Janitor Service 2025-05-14 03:46:44 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2025-05-29 03:59:51 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.