Search Issue Tracker
Third Party Issue
Votes
1
Found in
2022.3.24f1
2023.2.18f1
2023.3.0b10
6000.1.0a7
6000.2.0a1
6000.3.0a1
Issue ID
UUM-69244
Regression
No
“Uncaught RuntimeError” error when GZipStream is initialized with CompressionMode.Decompress and Code Optimization is set to with LTO in WebGL
Reproduction steps:
1. Open the attached project “ReproProj”
2. Go to File > Build Settings and select WebGL platform
3. Set Code Optimization to "Disk Size with LTO"
4. Build And Run
5. Press the “Decompress” button
Expected result: Button function is completed
Actual result: “Uncaught RuntimeError” error is thrown
Reproducible with: 2022.3.24f1, 2023.2.18f1, 2023.3.0b10
Couldn’t test with: 2021.3.37f1 (No "Disk Size with LTO" code omptimization option)
Reproducible on: macOS 14.3.1 (M1 Max), Windows 10
Not reproducible on: No other environment tested
Comments (1)
-
ANTONBORODA
Dec 02, 2024 19:13
Latest version of Unity 6 (29f1) does not work even when no LTO option is selected. The build crashes on any WasmCodeOptimization except for BuildTimes.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for bringing this issue to our attention and for taking the time to report it.
Following a thorough review of the reported problem, we have determined that the root cause lies within the Emscripten codebase. While we anticipate that this issue will be addressed in a future Emscripten update, we recommend avoiding the use of the LTO build option as a temporary workaround.
At this time, we will be closing this case. However, we encourage you to monitor upcoming Emscripten releases for relevant updates and improvements.
Thank you again for your valuable feedback and for helping us improve.
Resolution Note:
Thank you for bringing this issue to our attention and for taking the time to report it.
Following a thorough review of the reported problem, we have determined that the root cause lies within the Emscripten codebase. While we anticipate that this issue will be addressed in a future Emscripten update, we recommend avoiding the use of the LTO build option as a temporary workaround.
At this time, we will be closing this case. However, we encourage you to monitor upcoming Emscripten releases for relevant updates and improvements.
Thank you again for your valuable feedback and for helping us improve.