Search Issue Tracker
Fixed
Fixed in 1.8.3
Votes
0
Found in [Package]
1.8.1
1.8.2
Issue ID
BUR-2186
Regression
Yes
Burst compilation is taking almost twice longer after upgrading to Burst 1.8.1 and newer
How to reproduce:
1. Open the attached project “BurstBug”
2. Click Colossal Tools → Build Window
3. Click Build under the Build Settings field
4. Observe the compilation time in the Editor.log by searching “bcl.exe”
Expected result: Compilation time is similar to the compilation time using the older versions
Actual result: Compilation time is taking almost twice the compilation time in older versions
Reproducible with: 1.8.1 (2021.3.15f1, 2022.1.24f1, 2022.2.0b12, 2023.1.0a21), 1.8.2 (2021.3.15f1, 2022.1.24f1, 2022.2.0b12, 2023.1.0a21)
Not reproducible with: 1.8.0 (2021.3.15f1, 2022.1.0f1, 2022.2.0b12, 2023.1.0a21)
Couldn’t test with: Prior to 1.8.0 versions (Building time takes around an hour, which would make testing really long)
Reproducible on: Windows 11 Pro
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
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
Resolution Note (fix version 1.8.3):
The reason for the performance regression is that in 1.8.0, when doing a development build, full debug info wouldn't be generated, only line information. That was fixed in 1.8.1, which means the compilation of development builds take longer due to the extra amount of data being worked with.
I have added an option in "Player Settings > Burst AOT Settings" called "Debug Information Kind", which defaults to "Full". But users can set this to "Line Only" if they don't need full debug information for their development builds and would instead like the faster compilation.