Created attachment 146686 [details] Mem usage after 10 minutes SUMMARY Kwin starts wayland session using about 50MB of ram. If you keep using the PC, it will go up to huge amounts (got 1.5gb) One thing I noticed is that if you keep passing the mouse on the task manager to see the window thumbnail/preview it increases memory usage. Eventually it goes down a bit, but never at initial levels. Even after closing all windows/apps ram never goes down to initial levels (or near them) STEPS TO REPRODUCE 1. Just use the PC? OBSERVED RESULT High Ram Usage EXPECTED RESULT Low ram usage ADDITIONAL INFORMATION All window previews are black, don't know if that is related to "preview" functionality or not. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2
Forgot to mention that I'm using firefox (MOZ_ENABLE_WAYLAND=1) and watching a lot of youtube, don't know if those videos play a role as well.
Can you run heaptrack to track kwin's memory usage? heaptrack --pid $(pidof kwin_wayland)
(In reply to Vlad Zahorodnii from comment #2) > Can you run heaptrack to track kwin's memory usage? heaptrack --pid $(pidof > kwin_wayland) Quick question: this is a dump tool or do I need to keep it running while using the system?
Created attachment 146740 [details] heaptrack (400+ MB being used after closing all windows/apps)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
That heaptrack file shows: - peak of 53.3Mb used - most of that being from QQuickRenderControl::grab which is almost certainly Aurorae There's nothing wrong on the heap. That initial screenshot is including mmapped data which could be leaking, but isn't necessarily an indication of anything problematic.
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!