Search Issue Tracker
Third Party Issue
Votes
1
Found in
6000.0.54f1
6000.1.13f1
6000.2.0b12
6000.3.0a3
Issue ID
UUM-112943
Regression
No
WebGL build crashes when opening a ZipArchive entry and "Code Optimization" is not set to the default "Shorter Build Time"
How to reproduce:
1. Open the “IN-106873_TestZipload“ project
2. Open File > Build Profiles
3. Ensure “Code Optimization” is set to “Runtime Speed”
4. Build and Run
5. In the Build press the space bar
6. Observe crash
Reproducible with: 2023.1.0a6, 6000.0.54f1, 6000.1.13f1, 6000.2.0b12, 6000.3.0a3
Could not test with: 2023.1.0a1, 2023.1.0a5 (An instant runtime error after the build is created)
Reproducible on: macSO 15.5 (M1 Max), Windows 11 (by user)
Not reproducible on: no other environments tested
Note: Not reproducible with Code Optimization set to “Shorter Build Time”
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
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
- LocalizationSettings.InitializationOperation hangs when re-entering Play Mode with Domain Reload disabled
Resolution Note:
Thank you for reporting this bug to Unity.
After careful review, we have determined that the root cause of the issue lies with the upstream LLVM LTO optimizer (https://github.com/llvm/llvm-project: The LLVM Project is a collection of modular and reusable compiler and toolchain technologies).
The LTO optimizer is a special, last-stage optimizer in the native LLVM build chain. Unlike regular optimizers that work on individual functions, LTO analyzes and optimizes the entire codebase for additional improvements.
As a workaround in the current version of Unity, you can avoid triggering the LTO optimizer by performing a Development build or a Release build with the optimization set to “Shorter Build Time.” The LTO optimizer is only enabled for “Runtime Speed” and “Disk Size” build configurations.
Since this issue originates from a third-party component, we are closing this ticket as a "third party issue." If you have further questions or concerns, please let us know.