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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Add comment