Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.2f1
Issue ID
1119490
Regression
No
Unresponsive Editor caused by Shader Compilation
Steps:
1. Open repro project
2. Open the shader and uncomment the lines
#define foo bar.foo
foo;
3. Save the shader and go back to editor
4. Editor freezes
Reproducible in : 2018.3.2f1, 2019.1.0a4, 2019.1.0a12
Not-reproducible in : 2019.1.0a13, 2019.1.0a14 (correctly shows an error that foo is unrecognised)
Tested on Mac Metal
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment