-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when running project with error ERROR: Condition "flushing_cmd_queue != nullptr" is true.
#90363
Comments
That's #87721, CC @clayjohn @RandomShaper. |
When I run the demo project with dev 5 I just get this warning:
Turning off multi threaded rendering solves the issue. I can confirm this happens on master and is not fixed by #90268. Will need to debug further |
Okay, it is crashing on this line godot/core/templates/command_queue_mt.h Line 373 in 9d6bdbc
With this signal:
Call stack:
Its crashing after calling godot/servers/server_wrap_mt_common.h Lines 246 to 254 in 9d6bdbc
|
This diff fixes the crash, but I don't think it is the correct solution:
This skips the flush when another flush is occurring, it works because |
Tested versions
System information
Godot v4.3.dev (e5b4ef8) - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 Ti (NVIDIA; 31.0.15.5186) - AMD Ryzen 9 5900X 12-Core Processor (24 Threads)
Issue description
Upon running the TestCustomTextures Demo project it crashes with the error:
The TestCustomTextures Demo works in 4.2.1 Stable version.
Steps to reproduce
Open the TestCustomTextures Demo project and attempt to run it.
Note that it opens fine in the editor initially. It only crashes when you attempt to Play it.
Minimal reproduction project (MRP)
Use the TestCustomTextures Demo project.
Bisect results
83241ab is the first bad commit
commit 83241ab
Date: Mon Jan 29 14:47:50 2024 -0800
scene/resources/texture_rd.cpp | 186 ++++++++++++++++++++++-------------------
scene/resources/texture_rd.h | 9 ++
2 files changed, 108 insertions(+), 87 deletions(-)
The text was updated successfully, but these errors were encountered: