Search Issue Tracker
Won't Fix
Won't Fix in 1.8.X
Votes
0
Found in [Package]
1.8.19
Issue ID
BUR-2816
Regression
No
Significant increase in compilation time when Burst package is installed
How to reproduce:
1. Open the “U6CT.zip“ project
2. Press Assemblies > “Create 100 Assemblies” in the Toolbar
3. In any of the generated Assemblies (in “Assets/Assets/Core”) make any change to trigger a Script Reload
4. Observe the loading times
5. Install the Memory Profiler package from the Package Manager (to install the Burst package as a dependency)
6. Repeat step 3
7. Observe the loading times again
Expected result: The second Script Compilation Time takes roughly around the same time as in step 4
Actual result: The second Script Compilation Time takes double or more time than in step 4
Reproducible in: 1.8.0, 1.8.19 (2022.3.58f1, 6000.0.38f1, 6000.1.0b6, 6000.2.0a3)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Note: It’s increasingly noticeable with more Assembly scripts are generated
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.8.X):
There are no fixes planned for this Bug