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
- [Android] Light2D with Light type "Spot" does not work in the Player on some Pixel devices
- [Android] Loading the asset using an old reference returns null even when the "FormerlySerializedAs" attribute is used
- Crash on ParticleSystemTrailGeometryJob::RenderJobCommon when changing trail Mode change with a large particle count
- Mouse cursor does not revert to the default mouse cursor when pressing the "Add column" button in the Search window
- ArgumentException is thrown and textures become unreadable when AssetBundle.Unload(false) is called
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.