Search Issue Tracker
Fixed in 2019.3.X
Votes
4
Found in
2018.2.0b2
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1031630
Regression
No
Unity build process freezes when compiling shader
How to reproduce:
1. Open the "Shader_Crash.zip" project
2. Build the "16-Shader.unity" scene
Actual result: Unity freezes.
Reproducible with: 2019.2.0a3, 2019.1.0b1, 2018.3.4f1, 2018.3.0a1.
Notes:
On 2018.1 and 2018.2 the build completes, but Player crashes instantly. (Stack trace attached)
Errors are thrown during the building process:
"Assertion failed: Assertion failed on expression: 'ptr == NULL || !HAS_ROOT_REFERENCE(GET_CURRENT_ALLOC_ROOT_REFERENCE()) || GET_CURRENT_ALLOC_ROOT_REFERENCE() == GET_ROOT_REFERENCE(s_MonoDomainContainer, kMemMono)'"
"Assertion failed: Lz4 doesn't support input or output data size > INT_MAX"
---------------------------------------------
Unity is actually not frozen. Compile time and progress bar was improved.
Fixed in 2019.3.0a5, 2019.2.0b7.
Comments (1)
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
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
- Warnings due to obsolete Object.FindObjectsByType<T> usage and [SerializeReference] are logged when opening the Netcode for Entities setup scene
- Non-standard pointers cannot change Inspector values with arrow controls when crossing Inspector area
- No longer able to change the Toggle or Slider GameObjects' Target Graphic value and a NullReferenceException is thrown when the Target Graphic value is set to None at any point
GlowfishInteractive
Feb 05, 2019 13:34
I'm currently encountering this issue when upgrading a project from 2017.4.14 to the 2018 versions of Unity.
This is fully stopping us from creating a working build of our game !
As of 2018.3 the error has changed to the following message instead: "Standard: Too large shader binary (-1911378036 > max 2147483647 bytes) - compression failed. Try reducing the number of variants or shader complexity."
Potential helpful info: https://forum.unity.com/threads/standard-too-large-shader-binary-1911378036-max-2147483647-bytes-compression-failed-try-red.618550/?fbclid=IwAR3RzbnhARyEkrcPOD6DWn_n7Zd0jkn2TAGAoZ121DYX9TQPl3UmBl4yLlY#post-4144252