-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Manually running a schedule in a sub-world hangs #10032
Comments
can you do |
It's at 1.5.4:
Pinning it to 1.5.1 seems to resolve the issue! |
It might also be possible that the changes re-exposed this bug that we worked around before #7825 (comment). |
I encountered this in #9122. Examples with state transitions (like |
|
The cause of this (queueing task to local queue) was completely rolled back in async executor. |
Bevy version
0.11.3
What you did
I tried to run the main schedule in a "sub-world". The following demo program should terminate, but as long as the "sub-world" contains a system, it will hang. (Please note that in a more elaborate example some systems might even run before it hangs)
What went wrong
I expected the inner run_schedule to run and complete. After that, the outer system should continue (and terminate).
Instead it hangs, I assume there's a deadlock (here's an excerpt from GDB):
The text was updated successfully, but these errors were encountered: