Search Issue Tracker
Fixed
Votes
4
Found in [Package]
0.2.0-preview.18, 0.5.1-preview.11
Issue ID
1217026
Regression
No
Job Complete must be called before Scheduling another job with the same JobHandle
How to reproduce:
1. Open attached project "UnityRequests.zip" and scene "CollisionSystemTest"
2. Enter Play mode
3. Observe Console window
Expected result: "Entity Entity(1:1) collided with entity Entity(0:1)" are thrown
Actual result: errors are thrown(more detail in the notes)
Reproducible with: 2019.3.1f1 (0.2.0-prev.18, 0.5.1-prev.11), 2020.1.0a22(0.5.1-prev.11)
Could not test with: 2019.2.20f1(0.1.1-prev) and older (due to Entity errors in the console window)
Notes:
[2019.3 errors]
InvalidOperationException: The previously scheduled job CollisionSystem:CollisionSystemJob writes to the NativeArray CollisionSystemJob.UserJobData.NativeContainer. You must call JobHandle.Complete() on the job CollisionSystem:CollisionSystemJob, before you can read from the NativeArray safely.
[2020.1 errors]
InvalidOperationException: The previously scheduled job CollisionSystem:CollisionSystemJob writes to the UNKNOWN_OBJECT_TYPE CollisionSystemJob.UserJobData.NativeContainer. You must call JobHandle.Complete() on the job CollisionSystem:CollisionSystemJob, before you can read from the UNKNOWN_OBJECT_TYPE safely.
InvalidOperationException: The previously scheduled job CollisionSystem:CollisionSystemJob reads from the NativeArray<Velocity> CollisionSystemJob.InputVelocities. You are trying to schedule a new job Solver:ApplyGravityAndCopyInputVelocitiesJob, which writes to the same NativeArray<Velocity> (via ApplyGravityAndCopyInputVelocitiesJob.InputVelocities). To guarantee safety, you must include CollisionSystem:CollisionSystemJob as a dependency of the newly scheduled job.
And many more
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
supermeip
Jun 26, 2020 19:59
Im experiencing this issue on 2019.4