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
- [OSX][Settings] When using only the new ISX as Input Handling, mouse position and scroll are still detected by the old system.
- [Scripting] Input Action fails to re-enable after disabled.
- [MacOS] "Bloom" does not work in Standalone Build
- Mesh.CombineMeshes result has different normals if the original mesh has tweaked normals and scale
- [Hub] In licence error screen https://unity3d.com/unity/err/license redirects to not found website
Add comment