(01-12-2023, 06:36 AM)josemendez Wrote: Hi,
I'm unable to reproduce this. Could you describe under what situations does this happen?
This error is raised by Unity's job safety system. If it only happens in the editor, disabling the safety checks in the Jobs menu should get rid of it. This is of course not ideal, but shouldn't affect runtime behavior.
https://learn.microsoft.com/en-us/dotnet...ng-dispose
The boolean parameter in Dispose(bool) lets you know whether the method is called by a finalizer (similar to a destructor in C/C++) or by manually calling the Dispose() method. In both cases we need to release the safety handle, so the correct thing in this case is to ignore the parameter.
I have already passed on the testing project to you. Could you please confirm again