I think I’ll just abandon this odd curiosity given how esoteric and niche the thread crash is.
My wild guess, it’s somehow related to the Xwayland stubs that get compiled in Hyprland when building without Xwayland support. Or some bits of unused GL that get compiled out.
-DNO_XWAYLAND:STRING=true
BUT… I build the same way on my Intel laptop and this issue does not occur.
Hyprland 0.51.0 built from branch main at commit b10b9660004b3dfaf9e11a305d78f24955b089a4 dirty (screencopy: fix missing XBGR2101010 format with screencopy_force_8b ( 12125)).
Date: Sat Oct 25 06:57:46 2025
Tag: v0.51.0-109-gb10b96600, commits: 6527
Libraries:
Hyprgraphics: built against 0.2.0, system has 0.2.0
Hyprutils: built against 0.10.0, system has 0.10.0
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.3, system has 0.6.3
Aquamarine: built against 0.9.5, system has 0.9.5
flags set:
no xwayland
So, it’s specific to nVidia+Hyprland (sans Xwayland) and only affects Chromium versions since 140.x.
If I build vanilla Hyprland (with Xwayland)… on the nVidia system… issue does not occur. Wth?
Having absolutely zero use for the pesky chrome://gpu page whatsoever… this is just a Waste of Time™!