Hi Everyone,
I was wondering if any of you has even encoutered this issue with Kde Plasma Wayland and KRDP on Endeavour. I have installed the KRDP service to connect to a VM which has EOS installed on it. It runs plasma as DE but for some reason as soon as I connect to the VM with Remmina or KDRC the memory usage of the service start to increase until the kernel kills the service. It take a couple of minutes for the service to fill the ram and the swap. It’s not a small memory leak it goes up fast enough to make it barely usable (2 -3 minutes to fill 8 gb of ram). I’ve taken a look at the Kde bug list for KRdp and don’t really see a OOM issue beside this one : https://bugs.kde.org/show_bug.cgi?id=507949 which is not exactly what I have. Before creating a bug report on KDE I wanted to see if this is fixable in any way or related to EOS. Disconnecting does not make the KRdp service memory return to normal. It stays at the current value until the service is resetted by the kernel or restarted by me.
To recreate the issue you just need to connect to the vm with remmina with freerdp or krdc. THe ram should usage of KRdp should climb up pretty fast.
The VM :
System:
Host: eos-vm Kernel: 6.16.7-arch1-1 arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.4.5 Distro: EndeavourOS
Machine:
Type: Kvm System: QEMU product: Standard PC (i440FX + PIIX, 1996)
v: pc-i440fx-10.0 serial: <superuser required>
Mobo: N/A model: N/A serial: N/A BIOS: SeaBIOS
v: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org date: 04/01/2014
CPU:
Info: 6-core model: AMD Ryzen Threadripper 3960X bits: 64 type: MCP cache:
L2: 3 MiB
Speed (MHz): avg: 3823 min/max: N/A cores: 1: 3823 2: 3823 3: 3823 4: 3823
5: 3823 6: 3823
Graphics:
Device-1: Red Hat Virtio 1.0 GPU driver: virtio-pci v: 1
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: modesetting gpu: virtio-pci
resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: kms_swrast,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: mesa v: 25.2.2-arch1.2 renderer: llvmpipe
(LLVM 20.1.8 256 bits)
API: Vulkan Message: No Vulkan data available.
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Message: No device data found.
API: ALSA v: k6.16.7-arch1-1 status: kernel-api
Server-1: PipeWire v: 1.4.8 status: active
Network:
Device-1: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge
driver: piix4_smbus
Device-2: Red Hat Virtio network driver: virtio-pci
IF: ens18 state: up speed: -1 duplex: unknown mac: bc:24:11:4c:5c:93
IP v4: 192.168.5.24/24 type: dynamic noprefixroute scope: global
IP v6: fe80::985a:f743:5a2b:761b/64 type: noprefixroute scope: link
WAN IP: 67.230.150.170
Drives:
Local Storage: total: 64 GiB used: 20.46 GiB (32.0%)
ID-1: /dev/vda model: N/A size: 64 GiB
Partition:
ID-1: / size: 56.39 GiB used: 19.23 GiB (34.1%) fs: ext4 dev: /dev/vda1
Swap:
ID-1: swap-1 type: partition size: 6.4 GiB used: 1.23 GiB (19.2%)
dev: /dev/vda2
Sensors:
Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon
or lm-sensors.
Info:
Memory: total: 8 GiB available: 7.75 GiB used: 6.22 GiB (80.3%)
Processes: 185 Uptime: 16h 47m Shell: Bash inxi: 3.3.39
The Journal :
Sep 10 13:46:26 eos-vm systemd[763]: Starting KRDP Server...
Sep 10 13:46:26 eos-vm systemd[763]: Started KRDP Server.
Sep 10 13:46:27 eos-vm krdpserver[1673]: libEGL warning: failed to get driver name for fd -1
Sep 10 13:46:27 eos-vm krdpserver[1673]: libEGL warning: MESA-LOADER: failed to retrieve device information
Sep 10 13:46:27 eos-vm krdpserver[1673]: libEGL warning: failed to get driver name for fd -1
Sep 10 13:46:27 eos-vm krdpserver[1673]: MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
Sep 10 13:46:27 eos-vm krdpserver[1673]: libEGL warning: egl: failed to create dri2 screen
Sep 10 13:46:27 eos-vm krdpserver[1673]: org.kde.krdp: Listening for connections on QHostAddress(QHostAddress::Any) 3389
Sep 10 13:46:32 eos-vm krdpserver[1673]: org.kde.krdp: Initializing Freedesktop Portal Session
Sep 10 13:46:32 eos-vm krdpserver[1673]: org.kde.krdp: Session setup completed, start processing...
Sep 10 13:46:32 eos-vm krdpserver[1673]: org.kde.krdp: Started Freedesktop Portal session
Sep 10 13:46:32 eos-vm krdpserver[1673]: kpipewire_vaapi_logging: DRM device not found
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: New client connected: UNIX platform Unspecified version
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: Video stream initialized
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: Received caps:
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: RDPGFX_CAPVERSION_8 AVC: false YUV420: false
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: RDPGFX_CAPVERSION_81 AVC: true YUV420: true
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: RDPGFX_CAPVERSION_10 AVC: true YUV420: false
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: RDPGFX_CAPVERSION_101 AVC: true YUV420: false
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: RDPGFX_CAPVERSION_102 AVC: true YUV420: false
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: RDPGFX_CAPVERSION_103 AVC: true YUV420: false
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: RDPGFX_CAPVERSION_104 AVC: true YUV420: true
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: RDPGFX_CAPVERSION_105 AVC: true YUV420: true
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: RDPGFX_CAPVERSION_106 AVC: true YUV420: true
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: UNKNOWN_VERSION AVC: false YUV420: false
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: RDPGFX_CAPVERSION_107 AVC: true YUV420: true
Sep 10 13:46:38 eos-vm krdpserver[1673]: org.kde.krdp: Selected caps: RDPGFX_CAPVERSION_107
Sep 10 13:46:38 eos-vm krdpserver[1673]: kpipewire_record_logging: Hardware encoding is not supported on this device.
Sep 10 13:46:38 eos-vm krdpserver[1673]: [libx264 @ 0x7f288c3786c0] -qscale is ignored, -crf is recommended.
Sep 10 13:46:38 eos-vm krdpserver[1673]: [libx264 @ 0x7f288c3786c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
Sep 10 13:46:39 eos-vm krdpserver[1673]: [libx264 @ 0x7f288c3786c0] profile Constrained Baseline, level 6.1, 4:2:0, 8-bit
Sep 10 13:46:39 eos-vm krdpserver[1673]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QApplication(0x7ffdf0c301c0), parent's thread is QThread(0x55a277ab8390), current thread is QThr>
Sep 10 13:46:39 eos-vm krdpserver[1673]: kpipewire_dmabuf_logging: eglChooseConfig returned this many configs: 1
Sep 10 13:47:45 eos-vm krdpserver[1673]: QObject::killTimer: Timers cannot be stopped from another thread
Sep 10 13:47:45 eos-vm krdpserver[1673]: QObject::startTimer: Timers cannot be started from another thread
Sep 10 13:47:53 eos-vm krdpserver[1673]: QObject::killTimer: Timers cannot be stopped from another thread
Sep 10 13:47:53 eos-vm krdpserver[1673]: QObject::startTimer: Timers cannot be started from another thread
Sep 10 13:53:43 eos-vm systemd[763]: app-org.kde.krdpserver.service: A process of this unit has been killed by the OOM killer.
Sep 10 13:53:43 eos-vm systemd[763]: app-org.kde.krdpserver.service: Main process exited, code=killed, status=9/KILL
Sep 10 13:53:43 eos-vm systemd[763]: app-org.kde.krdpserver.service: Failed with result 'oom-kill'.
Sep 10 13:53:44 eos-vm systemd[763]: app-org.kde.krdpserver.service: Consumed 1min 20.868s CPU time, 6.3G memory peak, 5.5G memory swap peak.
Sep 10 13:53:44 eos-vm systemd[763]: app-org.kde.krdpserver.service: Scheduled restart job, restart counter is at 1.
Sep 10 13:53:44 eos-vm systemd[763]: Starting KRDP Server...
Sep 10 13:53:44 eos-vm systemd[763]: Started KRDP Server.
Any help would be appreciated.