Search Issue Tracker
Fixed in 1.6.0-pre.2
Votes
0
Found in [Package]
1.5.0-preview.3
Issue ID
1348234
Regression
Yes
Burst yields different results than mono when using a large (>= 2147483648L) readonly static long
How to reproduce:
1. Open the user's attached project
2. Open the SampleScene
3. Enter the Play mode
4. Observe the Console
Expected result: No visible errors present
Actual result: The 'Assertion failed' error appears in the Console
Reproducible with: Burst 1.5.0-pre.3, 1.5.6-preview.1 (2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b6, 2022.1.0a5)
Not reproducible with: Burst 1.4.9 (2019.4.29f1), 1.6.0-pre.2 (2019.4.29f1), 1.6.0-pre.3 (2018.4.36f1, 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b6, 2022.1.0a5)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment