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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
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.