Search Issue Tracker
Fixed
Fixed in 1.8.23
Votes
2
Found in [Package]
1.8.18
Issue ID
BUR-2773
Regression
No
[Android] Build fails with a "Burst compiler failed running" error when Burst Optimizations are enabled and a specific Job has the [BurstCompile] attribute
Reproduction steps:
1. Open the attached “IN-86100” project
2. Build the Player (File > Build Settings > Build)
Expected result: The Player is built successfully
Actual result: The build fails and the “Burst compiler failed running” error is shown
Reproducible with: 1.8.13 (6000.0.0b12), 1.8.18 (2022.3.51f1, 6000.0.24f1, 6000.1.0a1)
Couldn’t test with: 2021.3.45f1 (Errors when downgrading the project)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- Issue does not reproduce if:
a) “Enable Optimizations” in Burst AOT Settings is disabled
b) The [BurstCompile] attribute is removed on line 48 in the “Script.cs” script
- Only reproducible when building for the Android platform
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment