[nvidia] vram memory leak under Wayland

Bug #1974029 reported by Mateusz Łącki
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mutter
New
Unknown
mutter (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I use 3 monitors. When I turn two of then off and on, the "memory usage" shown by nvidia-smi grows by approximately 400 MB each cycle. When used video memory reaches maximum my card has (it ix GTX 970 with 4GB) the graphical system sort of crashes (desktop is not shown, one of the monitor does not show image at all).

This occurs only under Wayland.

Description: Ubuntu 22.04 LTS
Release: 22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.0c.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022
 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 18 14:50:11 2022
DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit()
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
 nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a]
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on iommu=pt
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago)
dmi.bios.date: 08/10/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5861
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X470-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
Mateusz Łącki (mateusz-lacki) wrote :
affects: ubuntu → xorg (Ubuntu)
summary: - vram memory leak under Wayland
+ [nvidia] vram memory leak under Wayland
affects: xorg (Ubuntu) → mutter (Ubuntu)
tags: added: leak nvidia nvidia-wayland
tags: added: wayland
Changed in mutter:
status: Unknown → New
tags: added: gnome-shell-leak
Revision history for this message
Mateusz Łącki (mateusz-lacki) wrote :

Still present in 22.10 beta.

tags: added: kinetic
Revision history for this message
Mateusz Łącki (mateusz-lacki) wrote :

Present in 22.10 proper.

Revision history for this message
willian (guns945) wrote (last edit ):

Same problem. Ubuntu 22.04. I constantly change the desktop from my main monitor, to a tv to mirroring. Picture shows large memory usage, but not from where it comes. If asked, I can provide additional info. RTX 3070 GPU.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mutter (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

willian, the image in comment #4 shows Xwayland is using the most VRAM. That might be an Xwayland bug or it might just be a resource-hungry app.

To identify potential apps you can run 'xwininfo' and the cursor will change to a cross whenever it is over an Xwayland app.

You can also run 'xrestop' to get a list of the most resource hungry Xwayland apps.

Revision history for this message
Mateusz Łącki (mateusz-lacki) wrote : Re: [Bug 1974029] Re: [nvidia] vram memory leak under Wayland

Hi,

In my case switching monitors on and off a few times increases the
memory usage from

   601MiB /  4096MiB

to

  2187MiB /  4096MiB

at the same time xresyop content does not change it is:
0600000    15    3    0    0   60     7609K      1K   7611K   ? mutter
guard w
1400000     1    1    0    1    7     7342K    216B   7342K   ? <unknown>
1a00000     1    1    1    2   10       78K      1K     79K   ? Qt
Selection O
0000000     1    0    2    0  108        0B      4K      4K   ? <unknown>
0a00000     2    0    1    0   17        0B      1K      1K 1862079
Skype [1]
1c00000     1    0    1    0    8        0B      1K      1K   ? Qt
Selection O
1800000     1    1    1    0    6        0B      1K      1K   ? <unknown>
0c00000     3    1    0    0   14        0B    432B    432B 1862079
skypeforlinu
0400000     3    1    0    0   13        0B    408B    408B 1862448 ibus-x11
0200000     2    1    0    0    7        0B    240B    240B 1862396
gsd-xsetting
0e00000     0    0    0    0    3        0B     72B     72B   ? <unknown>
2000000     1    1    0    0    0        0B     48B     48B   ? xrestop
1e00000     1    1    0    0    0        0B     48B     48B   ? <unknown>
1600000     0    1    0    0    0        0B     24B     24B   ? <unknown>
1200000     0    1    0    0    0        0B     24B     24B   ? <unknown>
1000000     0    0    0    0    1        0B     24B     24B   ? <unknown>
0800000     0    1    0    0    0        0B     24B     24B   ? <unknown>

Best,
Mateusz Łącki

On 3/13/23 02:30, Daniel van Vugt wrote:
> willian, the image in comment #4 shows Xwayland is using the most VRAM.
> That might be an Xwayland bug or it might just be a resource-hungry app.
>
> To identify potential apps you can run 'xwininfo' and the cursor will
> change to a cross whenever it is over an Xwayland app.
>
> You can also run 'xrestop' to get a list of the most resource hungry
> Xwayland apps.
>

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The issue discussed in comments #4-#6 probably isn't this bug so don't get distracted by it.

Revision history for this message
Mateusz Łącki (mateusz-lacki) wrote :

Still present in Ubuntu 23.04.

tags: added: lunar
Revision history for this message
Mateusz Łącki (mateusz-lacki) wrote :

I have checked again, and for me the problem is gone (likely due to some update).

Changed in mutter (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.