Search Issue Tracker
Fixed in Unity 2019.1
Votes
0
Found in
2018.2.6f1
Issue ID
1097215
Regression
No
Unity displays millions of lines of shader source in Editor log when the Shader Compiler crashes during builds
During builds for PS4 and PC, if the Shader Compiler fails, the entire shader source is output into the build log for each variant that failed to compile. This quickly creates bloated logs (biggest reported being 1.77 GB).
Resolution Note:
Now printing the shader source to editor log only in debug builds. Instead printing some more useful info (shader/pass name, keywords, etc) in case of shader compiler failure.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity Ads Package conflict with Moq framework
- Particle system trails sprites modifies unexpectedly when Texture Sheet Animation is enabled
- "Density" in "Buoyancy Effector 2D" description is inaccurate and difficult to understand
- Some Isometric Tiles are not Rendered on the Tilemap when using "Chunk" Mode on the Tilemap Renderer
- Input.GetKeyUp and Input.GetKeyDown always Return False when used in the Coroutine with WaitForEndOfFrame Return type
Add comment