godotengine / godotengine/godot
Crash issues Godot 4.5 & 4.6 Vulkan Forward+ (CAUSED BY SDFGI)
- Dominant language
- C++
- Stars
- 117k
- Forks
- 26.8k
- PR merge metrics
- PR metrics pending
Description
### Tested versions
Godot 4.5 Stable
Godot 4.6 Stable
### System information
Windows 11 - Godot 4.5 & Godot 4.6 Stable - Vulkan Forward+ - NVIDIA RTX 5080 Laptop
### Issue description
Constant crashes from Vulkan:
ERROR: Condition "err != VK_SUCCESS" is true. Returning: FAILED
at: fence_wait (drivers/vulkan/rendering_device_driver_vulkan.cpp:2760)
SERVER: Spawned meteor 4 scale=2.09 speed=21.72 at (-29.78945, 24.77301, -76.34289)
ERROR: Printing last known breadcrumbs in reverse order (last executed first.)
at: print_lost_device_info (drivers/vulkan/rendering_device_driver_vulkan.cpp:6146)
ERROR: Searching last breadcrumb. We've sent up to ID: 50525
ERROR: Last breadcrumb ID found: 50521
ERROR: Last known breadcrumb: BLIT_PASS
ERROR: Last known breadcrumb: UI_PASS
ERROR: Last known breadcrumb: BLIT_PASS
ERROR: Last known breadcrumb: UI_PASS
ERROR: Last known breadcrumb: BLIT_PASS
ERROR: Last known breadcrumb: UI_PASS
ERROR: Last known breadcrumb: BLIT_PASS
ERROR: Last known breadcrumb: UI_PASS
================================================================
CrashHandlerException: Program crashed with signal 11
Engine version: Godot Engine v4.6.stable.official (89cea143987d564363e15d207438530651d943ac)
Dumping the backtrace. Please include this when reporting the bug on: https://github.com/godotengine/godot/issues
[1] error(-1: no debug info in PE/COFF executable)
[2] error(-1: no debug info in PE/COFF executable)
[3] error(-1: no debug info in PE/COFF executable)
[4] error(-1: no debug info in PE/COFF executable)
[5] error(-1: no debug info in PE/COFF executable)
[6] error(-1: no debug info in PE/COFF executable)
[7] error(-1: no debug info in PE/COFF executable)
[8] error(-1: no debug info in PE/COFF executable)
[9] error(-1: no debug info in PE/COFF executable)
[10] error(-1: no debug info in PE/COFF executable)
[11] error(-1: no debug info in PE/COFF executable)
[12] error(-1: no debug info in PE/COFF executable)
[13] error(-1: no debug info in PE/COFF executable)
[14] error(-1: no debug info in PE/COFF executable)
[15] error(-1: no debug info in PE/COFF executable)
[16] error(-1: no debug info in PE/COFF executable)
[17] error(-1: no debug info in PE/COFF executable)
[18] error(-1: no debug info in PE/COFF executable)
[19] error(-1: no debug info in PE/COFF executable)
[20] error(-1: no debug info in PE/COFF executable)
[21] error(-1: no debug info in PE/COFF executable)
[22] error(-1: no debug info in PE/COFF executable)
-- END OF C++ BACKTRACE --
================================================================
This is all it gives despite adding --accurate-breadcrumbs and other logs commands, it happens randomly and doesn't seem tied to a specific gameplay events as I've tried disabling one by one every features of the game
Had this issue on Godot 4.5 and upgrading to 4.6 did not fix it
### Steps to reproduce
I have no idea it seems untied to gameplay events or UI creation
### Minimal reproduction project (MRP)
Working on one
Contributor guide
Research direction
Start with drivers/vulkan/rendering_device_driver_vulkan.cpp, especially fence_wait and print_lost_device_info, using the supplied Vulkan breadcrumbs and crash output. A minimal reproduction project is still being prepared, and the issue provides no reliable reproduction steps or named test. Done would require reproducing the SDFGI-related crash and verifying that the Vulkan device-loss failure no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100