Bug Report: Wayland-only: dmaAllocMapping_GM107 VA mapping failures (does not reproduce on X11)

I can reliably reproduce this issue with a specific trigger.

System:

  • GPU: GeForce RTX 3060 12GB
  • Driver: 595.58.03 (latest production branch)
  • Kernel: 6.19.12-1-cachyos
  • OS: CachyOS based on Arch Linux
  • Desktop: KDE Plasma 6.6.4 Wayland
  • Browser: Chromium-based (tested both Helium Browser and Google Chrome - same result)

Reproduction:

Navigating to https://m3.material.io/get-started reliably triggers the crash every time. The page loads briefly, then the tab freezes and the renderer process crashes with SIGILL. No extended usage or waiting required, it happens within seconds of the page loading.

Another page on the same site - https://m3.material.io/styles/shape/overview-principles - goes further and freezes the entire system, requiring a hard reboot. Unlike the get-started page which only crashes the renderer process, this one escalates to a full system hang immediately.

Relevant dmesg output:

kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.
kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:274
kernel: resource: resource sanity check: requesting [mem 0x00000000bf4f0000-0x00000000c02fffff], which spans more than 0000:01:00.0 [mem 0xb0000000-0xbfffffff 64bit pref]
kernel: caller __nv_drm_gem_nvkms_map+0x94/0x110 [nvidia_drm] mapping multiple BARs
kernel: hrtimer: interrupt took 18635980 ns
kwin_wayland[1420]: Pageflip timed out! This is a bug in the nvidia-drm kernel driver

Coredump from renderer process:

Signal: 4 (ILL)
Stack trace of thread:
#0  0x0000562c191f5458 n/a (n/a + 0x0)

What I’ve tested:

  • --disable-gpu → no crash (confirms GPU path is the trigger)
  • Firefox with GPU acceleration → works fine on the same page

Additional findings:

All <video> elements on affected pages use preload="auto" autoplay muted loop, causing Chromium to decode all videos simultaneously on page load. The main page https://m3.material.io has 1 video and works fine. The https://m3.material.io/get-started page has 10 simultaneous autoplay videos and crashes the renderer. The https://m3.material.io/styles/shape/overview-principles page has 7 simultaneous autoplay videos and freezes the entire system. Firefox handles all three pages without issues.

Happy to provide any additional logs or run diagnostic commands if it helps narrow this down. The fact that this is 100% reproducible on a specific URL should hopefully make it easier to debug on your end.
nvidia-bug-report.log.gz (362.3 KB)