Public bug reported:
## Environment
- Ubuntu 26.04 LTS
- GNOME Shell: 50.1-0ubuntu1.5
- libmutter-18-0: 50.1-0ubuntu2.5
- Kernel: 7.0.0-43-generic
- CPU: AMD Ryzen 7 7800X3D
- GPU: NVIDIA GeForce RTX 3060 (GA106)
- Session: Wayland
- Reproduced with NVIDIA drivers:
- 580.178.04
- 595.99.02 (open kernel module)
- 615.71.09 (open kernel module)
Primary monitor:
- LG TV
- 3840x2160 @ 119.88 Hz
- VRR normally enabled
- Scale 2.0
Secondary monitor:
- 1920x1080 @ 60 Hz
- Scale 1.0
The issue was also reproduced with both monitors at scale 2.0 and the
secondary monitor at 3840x2160 @ 30 Hz.
A Looking Glass B6 client is usually running, but closing it after the
problem starts does not restore normal CPU usage. The VM uses an AMD iGPU
through vfio-pci; the host compositor uses only the RTX 3060.
## Actual behavior
After login, gnome-shell initially uses approximately 10–20% CPU.
Over time, CPU usage increases continuously, eventually reaching 90–100%
of one CPU thread. This causes severe desktop stuttering and can reduce
the perceived frame rate from approximately 120 FPS to 40 FPS.
Depending on the session, clear degradation appears after approximately
1–6 hours. Increased video/compositor activity can accelerate it, but
the problem also occurs without a deliberate stress test.
Logging out and logging back in resets the problem temporarily.
Closing Looking Glass, closing the game or stopping video playback after
the degradation starts does not reliably reset the accumulated state.
## Profiling
perf consistently shows most CPU time in NVIDIA's libnxegl.so, in DRM
framebuffer creation and atomic KMS property handling.
Example with driver 580.178.04:
- 53.99% KMS thread: libnxegl.so — drmModeAddFB2WithModifiers
- 26.74% KMS thread: libnxegl.so — drmModeAtomicAddProperty
- 11.11% gnome-shell: libnxegl.so — drmModeAddFB2WithModifiers
Example with driver 595.99.02:
- 44.41% gnome-shell: libnxegl.so — drmModeAddFB2WithModifiers
- 18.63% KMS thread: libnxegl.so — drmModeAtomicAddProperty
- 12.81% KMS thread: libnxegl.so — drmModeAddFB2WithModifiers
The same general libnxegl/KMS path remains dominant across sessions.
## Tests that did not fix the problem
- NVIDIA 580, 595 and 615
- Disabling VRR
- Using the same scale on both monitors
- Reducing the secondary monitor to 4K @ 30 Hz
- Stopping gnome-remote-desktop.service
- MUTTER_DEBUG_USE_KMS_MODIFIERS=0
The modifiers setting changed part of the profile from
drmModeAddFB2WithModifiers to drmModeAddFB2, but the progressive CPU
growth still returned.
## Resource checks
While CPU usage was degraded:
- System RAM remained normal.
- NVIDIA BAR1 usage remained stable.
- /sys/kernel/debug/dma_buf/bufinfo remained at 801 lines over multiple
one-minute samples.
- DRM framebuffer debugfs files remained at 80 lines over the same
samples.
Therefore, there is no obvious continuous growth in the visible DRM
framebuffer or DMA-BUF object counts.
## Single-monitor and KWin comparisons
With the secondary monitor disabled and a fresh GNOME login, gnome-shell
remained approximately stable.
A controlled multi-window 4K YouTube stress test caused a temporary CPU
increase, but CPU usage subsequently returned to approximately 10–15%
instead of remaining degraded.
Under KDE Plasma Wayland, using the same dual-monitor setup and NVIDIA
driver, kwin_wayland remained approximately in the 9–16% CPU range during
the initial comparison, without the progressive growth seen in Mutter.
## Expected behavior
gnome-shell CPU usage should remain approximately bounded over time and
should return to its baseline after video or compositor-heavy workloads.
Changing the number of active monitors should not leave the compositor in
a permanently degraded state.
## Attachments
I can provide:
- perf recordings and perf report output from degraded sessions
- long-running pidstat logs showing the progressive CPU growth
- gdctl show output
- journal excerpts
- additional comparisons under specific display configurations
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: libmutter-18-0 50.1-0ubuntu2.5
ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14
Uname: Linux 7.0.0-43-generic x86_64
ApportVersion: 2.34.1-0ubuntu0.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Nov 13 08:39:41 2026
InstallationDate: Installed on 2024-11-10 (732 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64
(20240827.1)
SourcePackage: mutter
UpgradeStatus: Upgraded to resolute on 2026-10-28 (15 days ago)
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute wayland-session
** Attachment added: "markmap.svg"
https://bugs.launchpad.net/bugs/2174365/+attachment/6017524/+files/markmap.svg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2174365
Title:
GNOME Shell CPU usage grows continuously on dual-monitor NVIDIA
Wayland; libnxegl framebuffer/KMS operations dominate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2174365/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs