https://bugs.kde.org/show_bug.cgi?id=523098
Bug ID: 523098
Summary: KDE 6.7 runs Fedora 43 Guest VM out of memory running
under VMWare Workstation hypervisor with 3D
acceleration enabled
Classification: Plasma
Product: kwin
Version First 6.7.1
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: wayland-generic
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
Upgrading a Fedora 43 Guest Virtual Machine running under VMWare Workstation to
KDE version 6.7 results in a rapid memory leak in the VM Guest if the guest has
3D acceleration enabled in the Hypervisors settings for that guest.
This results in the OOM killer terminating the KDE session (on the VM Guest)
within a minute or two after booting the Guest.
System Monitor in the guest shows the memory/swap utilization continuously
rising until memory is exhausted. System Monitor does not seem to show a
specific process as using this memory though.
This is with the host running Windows 11 25H2, and using VMWare (Broadcom)
Workstation hypervisor version 25H2u1 (running on that Windows 11 host).
This happens if the Host has '3D Acceleration' enabled for the Guest. It does
not happen in the Workstation Display profile for the Guest VM has 3D
acceleration disabled.
I do not see this problem when the Fedora 43 guest VM is running KDE Plasma
version 6.6.5-2.fc43 with 3D acceleration enabled. Upgrading the same Fedora
43 Guest to KDE version 6.7.2-2.fc43 shows this fatal problem.
The graphics processor in the guest is listed as "SVGA3D; Build:Release: LLVM;
Virtual". This is presumably the VMWare Workstations virtual graphics card for
the guest.
STEPS TO REPRODUCE
1. Install or upgrade a Fedora 43 Guest (using KDE Plasma) on a Windows 11 Host
system running VMWARE Workstation hypervisor version 25H2u1. Fedora 43
currently uses KDE Plasma 6.7 after being fully updated. (It was recently using
KDE 6.6.5).
I gave the Guest VM 20 GB of ram space to use.
Ensure that the Guest's virtual machine setting for
"Hardware / Display / 3D Graphics / Accelerate 3D graphics" is checked.
2. Log in to the Guest and (quickly) start System Monitor to see the Guests
memory utilization.
OBSERVED RESULT
Total system memory utilization rapidly rises over the course of a minute or
two until it tries to use all available memory.
Performance rapidly becomes sluggish.
The OOM killer starts killing things off, and eventually you are back to the
login panel.
3) Then, end the guest VM. Change the Guest's virtual machine setting for
"Hardware / Display / 3D Graphics / Accelerate 3D graphics" to unchecked.
Start the guest again and log back in. Things now appear to work without
any obvious memory leaks.
EXPECTED RESULT
The guest system runs normally without a memory leak (as it did with KDE Plasma
6.6.5), with guest VM settings set to either 3D accelerated enabled or
disabled..
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 43
KDE Plasma Version: 6.7.2
KDE Frameworks Version: 6.28.0
Qt Version: 6.10.2
ADDITIONAL INFORMATION
Guest is using open-vm-tools-13.1.0-2.fc43 (as provided by Fedora 43 update).
In both cases (Working 6.6.5 and problematic 6.7.2) I was using Fedora 43
with Mesa 25.3.6-3.fc43 and kernel version 7.1.3-100.fc43 at the time.
Graphics Platform: Wayland
Tags: "VMware SVGA3D", "virtual machine"
--
You are receiving this mail because:
You are watching all bug changes.