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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Add comment