Search Issue Tracker
Fixed in 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).
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
- [Performance Regression] AnimatorEditorTests Rebind Big Hierarchy 341 Transform
- [Performance Regression] LogTests DebugLogWarning has regressed in performance
- [Performance Regression] ClassListSelector_AddNewElements has regressed in performance
- [Performance Regression] UIElementsStyling: ClassListSelector_AddNewElements test has regressed
- [Performance Regression] UIElementsStyling NameSelector_AddNewElements has regressed from 18.4
Resolution Note (fix version 2019.1):
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.