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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.