Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.8.3
Issue ID
BUR-2280
Regression
Yes
Build fails to compile when using burst compiling
Steps to reproduce:
1. Open the “TestECSVersion” project
2. Build And Run
Expected result: Builds and runs the project
Actual result: Build failed to compile with errors
Reproducible with: 1.8.0 (2022.2.0a16), 1.8.3 (2022.2.0a16, 2022.2.9f1, 2023.1.0b7, 2023.2.0a5)
Not reproducible with: 1.6.6 (2022.2.0a16), 1.7.4 (2022.2.0a16), 1.8.0-pre.2 (2022.2.0a16), 1.8.3 (2020.3.45f1, 2021.3.20f1, 2022.2.0a15)
Reproduced on: macOS Monterey 12.2 (Intel)
Errors:
- Library/Bee/artifacts/MacStandalonePlayerBuildProgram/AsyncPluginsFromLinker: Failed to find entry-points:
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun () (at /Users/bokken/build/output/unity/unity/Editor/Mono/BuildPlayerWindow.cs:188)
- Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/AsyncPluginsFromLinker failed with output:
UnityEditor.Build.BuildFailedException: Burst compiler (1.8.3) failed running
Note: The issue is in both Editor and package versions combined
Comments (1)
-
Eugene_Hip_Hop
Aug 15, 2023 13:41
I have the same error in Unity 2022.3.7f1 and in 2022.2.14f1, I can't find how to solve the problem :(
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note:
There are no fixes planned for this Bug