Search Issue Tracker
Fixed
Fixed in 6000.0.58f1, 6000.2.5f1, 6000.3.0b1
Votes
0
Found in
6000.0.55f1
6000.1.16f1
6000.2.0f1
6000.3.0a4
Issue ID
UUM-114084
Regression
Yes
"Runtime Error: unreachable" during initialization when building the project for WebGL with code optimization
Steps to reproduce:
1. Make sure the iOS player is installed to avoid console errors
2. Open the “user’s attached project”
3. Go to File/Build Profiles through the Main Menu
4. Switch the Build Profile to WebGL
5. Select any of the following Code Optimization options: Runtime Speed, Runtime Speed with LTO, Disk Size, Disk Size with LTO
5. Build and Run
6. Observe the error after the build has finished
Reproducible with versions: 6000.0.55f1, 6000.1.16f1, 6000.2.0f1, 6000.3.0a4
Couldn’t test with versions: 2021.3.54f1, 2022.3.65f1, 2023.2.20f1 (due to compiler and package errors)
Reproducible on: macOS 15.5 (M1 Max), Windows 11 (user)
Not reproducible on: no other environment tested
Note: not reproducible when running a Development Build
Workarounds:
- Disabling string compression when saving prefs in WebGL
- Disabling the "Compress Responses" option in Playfab settings
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animator Controller Layer name stays unchanged in Layers tab when renamed from Inspector
- [RenderingDebugger]Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
- [Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
- Crash on memcpy_repmovs when selecting NavMesh Agent objects while in Play Mode in a specific scene
Add comment