Crash under GPU load
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 237
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 1
Description
Wayfire version
0.10.1-746bc7e9 (Apr 10 2026) branch makepkg wlroots-0.19.3
GPU / Driver
$ glxinfo -B
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 8188 MB
Total available memory: 8188 MB
Currently available dedicated video memory: 7381 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 580.142
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6.0 NVIDIA 580.142
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 580.142
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
$ vulkaninfo --summary
Vulkan Instance Version: 1.4.341
Instance Extensions: count = 24
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 5
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_portability_enumeration : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
VK_LUNARG_direct_driver_loading : extension revision 1
VK_NV_display_stereo : extension revision 1
Instance Layers: count = 2
--------------------------
VK_LAYER_NV_optimus NVIDIA Optimus layer 1.4.312 version 1
VK_LAYER_NV_present NVIDIA GR2608 layer 1.4.312 version 1
Describe the bug
With a high GPU load, sometimes Wayfire suddenly ends the session. It's quite difficult to track the exact cause, but it always happens under high (and even medium) GPU load, for example: Minecraft with shaders, render in Blender.
Wayfire crashes precisely when the GPU is under load.
Wayfire crashes suddenly, then, after few seconds, SDDM shows.
This is very annoying because playing games turns into Russian roulette, and rendering projects at work turns into a nightmare.
I suspect it's something like a malloc error (returns NULL pointer and use it after that, although stable systems should handle the returned NULL pointers without crash and using NULL pointers) when there is not enough video memory or something like that, but I don't know for sure.
What to do?
Should I try to start rendering in Blender when Wayfire is running with debug? But which flags should I use? Something like this? WAYLAND_DEBUG=1 WAYFIRE_DEBUG=1 wayfire 2> wayfire.log
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by reproducing the crash with Minecraft shaders or a Blender render while collecting the proposed Wayfire log and GPU details; done means identifying a reproducible cause and documenting a verified fix or diagnostic result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100