Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.1.19f1
2023.2.0b17
2023.3.0a13
Issue ID
UUM-56321
Regression
Yes
The values for "Levels" and "Included DLLs" are consistently zero in the Editor.log build report when the project is built
Reproduction steps:
1. Open the “FAV_repro_NewUnityDefaultProject“ project
2. Open the Build Settings window
3. Build project
4. Open {{%LOCALAPPDATA%\Unity\Editor\Editor.log}} file
5. Observe Build Report
Expected result: Usage values of Levels and Included DLLs categories are not 0.0 kb
Actual result: The usage values for the Levels and Included DLLs categories are consistently 0.0 kilobytes
Reproducible with: 2021.2.0a13, 2021.3.32f1, 2022.3.13f1, 2023.1.19f1, 2023.2.0b17, 2023.3.0a13
Not reproducible with: 2021.2.0a12
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2023.3.X):
Fixing this in the new incremental build pipeline would be costly. Both implementation wise as well as affecting performance. Since very few users seem to depend on this feature we opted to remove the data rather than fixing it.