Bug 506934 - Memory leak on krdpserver
Summary: Memory leak on krdpserver
Status: RESOLVED WORKSFORME
Alias: None
Product: KRdp
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.4.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-12 05:48 UTC by Guillermo
Modified: 2025-08-20 03:47 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Guillermo 2025-07-12 05:48:02 UTC 
SUMMARY

Starting krdpserver either manually or automatically, the Resident memory grows (seen using top)


STEPS TO REPRODUCE
1. start krdpserver
2. start top, sort by memory
3. move any window

OBSERVED RESULT

krdpserver process consumed memory grows rapidly.


EXPECTED RESULT

krdpserver process consumed memory not growing.

SOFTWARE/OS VERSIONS
(VMWare virtual machine)
Operating System: EndeavourOS 
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Xeon® Platinum 8362 CPU @ 2.80GHz
Memory: 31.3 GiB of usable RAM

ADDITIONAL INFORMATION
Comment 1 TraceyC 2025-07-21 17:04:23 UTC 
Thanks for the bug report. Can you attach a screenshot of top when krdpserver is using a lot of memory?
Comment 2 Bug Janitor Service 2025-08-05 03:46:37 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 3 Bug Janitor Service 2025-08-20 03:47:02 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.