Created attachment 182886 [details] System Info Screenshot *** 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 connected to KRDP session from Windows RDP client, KRDP application uses system ram until full. Disconnecting RDP session stops usage but does not let it go (ram). STEPS TO REPRODUCE 1. Install of KRDP 2. Add user to KDE KRDP settings 3. Enable KRDP 4. Connect to host using Windows RDP Client 5. Log into system 6. Monitor system ram usage increase, more updates on screen faster ram fills. OBSERVED RESULT System RAM is used until Kernel closes RDP session due to memory usage and kills KRDP pid, freeing up memory. EXPECTED RESULT KRDP should not keep increasing RAM usage. SOFTWARE/OS VERSIONS Windows: Windows 11 Pro 23H2 (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Arch Linux Kernel 6.15.4-arch2-1 (64bit) KDE Plasma Version: 6.4.2 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 ADDITIONAL INFORMATION Graphics Platform: Wayland Running in Proxmox 8.3.4 VM (4 x vCPU, 6GB vRAM)
I tried all sorts of things but I can't reproduce this on master. Could you maybe try to run krdpserver through hotspot https://github.com/KDAB/hotspot and upload the recording or a screenshot of the flamegraph for inspection.
Created attachment 182924 [details] Flamegraph Export Flamegraph image of process during issue
Created attachment 182925 [details] Hotspot Parser File Export of Hotspot Parser during issue
Video capture of issue, logging into host with Windows 11 RDP Client. Memory ticks up faster with more screen activity till kernel kills process. https://youtu.be/0YPL46OJM8A
Oh sorry! I am a muppet. Hotspot is for cpu usage analysis, we'll want the data from running heaptrack https://invent.kde.org/sdk/heaptrack 😅
Created attachment 183112 [details] Heaptrack of krdpserver Added Heaptrack
Yeah that pretty much looks like a leak in mesa not our code. You appear to be missing debug symbols though. Could you do another recording but first run debuginfod-find debuginfo /usr/lib/libgallium-25.1.4-arch1.2.so to fetch the debug symbols. I hope that works anyway
🐛🧹 ⚠️ 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!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.