Search Issue Tracker
Fixed in 1.4.0-preview.4
Votes
0
Found in [Package]
1.4.0-preview.3
Issue ID
1221339
Regression
No
Running specific test when Burst Compiler is enabled causes System.IndexOutOfRangeException
How to reproduce:
1. Open the attached "project.zip" project
2. Select Jobs Menu bar -> Burst -> Enable Compilation
3. Open the Test Runner Window -> search for "Missing" Test
4. Select the Test -> click on "Run selected"
5. Repeat steps 2-4
Expected result: There are no "System.IndexOutOfRangeException" errors in Console Window
Actual result: There are "System.IndexOutOfRangeException: Index {0} is out of range of '{1}' Length." errors in Console Window
Reproducible with: 2019.4.8f1, 2020.1.2f1, 2020.2.0a20
Reproducible with Burst Package versions: 1.1.3 - preview.3, 1.4.0-preview.3
Notes:
- Could not reproduce on 2018.4 and older versions because Dots were not introduced in these versions yet
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 1.4.0-preview.4):
Package fix available in Unity 2018.4.0f1 and above