You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is actually an issue in the version of ZeroAllocJobScheduler that is currently being used in Arch.
As far as I can tell this has been fixed in more recent versions of that library.
Currently when the JobScheduler is disposed, it notifies a cancellation token and disposes a ManualResetEvent.
This does not correctly cause the worker thread to exit.
The worker thread is stuck waiting on line 53 above. Calling Dispose on the MRE does not stop waiting (tested on .net 8.0 but I don't think this has changed recently). Of course because the thread is stuck waiting, the cancellation token does nothing.
In my project this caused my game to not close properly, and for unit tests to run indefinitely.
I am leaving this issue here to let other people know that they should fork and fix until the new version of ZeroAllocJobScheduler has been put in to Arch.
The text was updated successfully, but these errors were encountered:
This is actually an issue in the version of ZeroAllocJobScheduler that is currently being used in Arch.
As far as I can tell this has been fixed in more recent versions of that library.
Currently when the JobScheduler is disposed, it notifies a cancellation token and disposes a
ManualResetEvent
.This does not correctly cause the worker thread to exit.
The worker thread is stuck waiting on line 53 above. Calling Dispose on the MRE does not stop waiting (tested on .net 8.0 but I don't think this has changed recently). Of course because the thread is stuck waiting, the cancellation token does nothing.
In my project this caused my game to not close properly, and for unit tests to run indefinitely.
I am leaving this issue here to let other people know that they should fork and fix until the new version of ZeroAllocJobScheduler has been put in to Arch.
The text was updated successfully, but these errors were encountered: