Search Issue Tracker
Fixed
Fixed in 1.8.19
Votes
0
Found in [Package]
1.8.18
Issue ID
BUR-2797
Regression
No
Burst error BC1003 is thrown when Burst compiles
How to reproduce:
1. Open the “IN-91465_repro“ project
2. Observe the Console
Expected result: Errors are not thrown
Actual result: BC1003 error is thrown
Reproducible with: 1.8.13 (2022.3.56f1), 1.8.18 (2022.3.56f1, 6000.0.35f1, 6000.1.0b3)
Reproducible on: Windows 10, macOS 15.1.1 (Intel)
Not reproducible on: No other environment tested
Error: (0,0): Burst error BC1003: Unexpected empty method body `Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle.NewStaticSafetyId(byte* ownerTypeNameBytes, int byteCount)`
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 GameObjects in a subscene are not rendered when using custom shaders and ECS until the Game view resolution changes
- Crash on AudioManager::InitFMOD when performing various actions in the Editor
- webGLBuildSubtarget resets to Generic when it gets changed in build script
- Publishing Settings are shared across different custom Build Profiles when modifying Build options
- deltaTime and unscaledDeltaTime discrepancy when Player window is moved to secondary monitor and VSync is enabled
Resolution Note (fix version 1.8.19):
There was a small bug in the implementation of the NewStaticSafetyId in Burst that would (without a specific attribute attached) cause it to error upon invocation. This is now fixed.