Search Issue Tracker
By Design
Votes
0
Found in
6000.0.54f1
6000.1.12f1
6000.2.0b10
Issue ID
UUM-111893
Regression
No
[Android] Crash due to running out of memory when compiling shaders for an Android build
How to reproduce:
1. Open the “ReproProject.zip“ project
2. Build for Android
Expected result: The “.apk“ builds successfully
Actual result: During the shader compilation in the building process crash happens do to the memory running out
Reproducible with: 6000.0.54f1, 6000.1.12f1, 6000.2.0b2, 6000.2.0b10
Not reproducible with: 6000.3.0a2
Could not test with: 2022.3.64f1 (Could not resolve compilation errors)
Fixed in: 6000.2.0a1
Reproducible environment: macOS 15.4.1 (M4 Max), Windows 10 (Reporters)
Not reproducible environment: No other environment tested
Notes:
- Does not reproduce when building Standalone
- Reproduces with both Vulkan and OpenGLES3 Graphic API
- Does not reproduce on a MR Multiplayer Tabletop Template when adding the affecting shader to Always Include Shaders in the Graphics settings
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
- Specular lighting visible in a camera with Path Tracing when Preserve specular lighting is disabled in observed material
- Cinemachine package throws CS1061 errors in the Console when installed in a project that has HDRP and URP installed
- Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
Resolution Note:
The shader in question tries to process 2.199.023 million variants (that's something like 2.2 trillion). The allocation that fails needs 77 GB.
The solution here is to remove this shader from always included shaders, and include only the variants that are needed.