Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.15f1
2021.2
2022.1
Issue ID
1361704
Regression
No
Using a NativeList.ParallelWriter in an IJobParallelFor completes in out of order thread results
Reproduction steps:
1. Open the attached project "1361704repro.zip"
2. Go to Assets/Scenes/"SampleScene"
3. Enter Play mode and observe the Console window
Expected result: Thread results are in order
Actual result: Thread results are out of order
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.24f1, 2021.2.0b14, 2022.1.0a11
Notes:
-Changing the IJobParallelFor that populated the NativeList with NativeList.ParallelWriter.AddNoResize to be IJobFor fixed the issue
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This is expected behavior. User cannot expect specific order when list is populated in parallel. If sorted order is desired, user must run sort after the list is populated.