Bug 443979 - Memory leak when using Wayland session
Summary: Memory leak when using Wayland session
Status: RESOLVED DOWNSTREAM
Alias: None
Product: frameworks-kded
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.87.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2021-10-18 16:44 UTC by Ahmed
Modified: 2021-11-08 09:10 UTC (History)
2 users (show)

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


Attachments
A screenshot for the result. (47.53 KB, image/png)
2021-11-04 16:32 UTC, Ahmed
Details
heaptrack output file. (875.19 KB, application/zstd)
2021-11-04 16:35 UTC, Ahmed
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ahmed 2021-10-18 16:44:43 UTC
SUMMARY
When I use RetroArch on Wayland, the memory usage increases 100mb every few seconds.

STEPS TO REPRODUCE
1. Starts Wayland session.
2. Open RetroArch (currently version 1.9.11)

OBSERVED RESULT
The memory usage increases 100mb every few seconds.

EXPECTED RESULT
RetroArch to behave the same as on X11.

SOFTWARE/OS VERSIONS 
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I noticed also that Plasmashell increases in size after using it for a little while.
Comment 1 Ahmed 2021-10-25 20:28:20 UTC
The same issue happens with KDE Plasma 5.23.1 - KDE Frameworks 5.87.0
Comment 2 David Redondo 2021-11-04 09:01:37 UTC
Can you try to run/attach heaptrack to the offending process and check what causes this? It would be awesome if you could also provide a screenshot of the results  https://invent.kde.org/sdk/heaptrack
Comment 3 Ahmed 2021-11-04 16:32:57 UTC
Created attachment 143208 [details]
A screenshot for the result.
Comment 4 Ahmed 2021-11-04 16:35:12 UTC
Created attachment 143209 [details]
heaptrack output file.
Comment 5 David Redondo 2021-11-08 09:10:32 UTC
Maybe I misunderstood earlier but retroarch is leaking memory? Then it's not a kde bug, please report it to retroarch