Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4.3f1
2020.2
Issue ID
1265143
Regression
No
[Critical] Editor crashes when #line directive is misplaced outside shader's block of code
How to reproduce:
1. Create a new 3D template project
2. Create a new Standard Surface Shader and open it
3. Add "#line 0" directive right after the shader's code ending bracket
4. Save the shader and focus the Editor
Expected result: The editor throws an error due to invalid input once the shader is recompiled
Actual result: The Editor crashes
Reproducible with: 2018.4.26f1, 2019.4.6f1, 2020.1.1f1, 2020.2.0a20
Notes:
1. When 2018.4.26f1 version is used, a crash pop-up is thrown after the shader is recompiled, however, the Editor does not actually crash and can be used afterward. This happens the only after the first shader recompile. Subsequent changes to the shader do not lead to a thrown crash pop until the Editor is reloaded(Track_1265143_V1)
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
- NativeArray can not be accessed when making a second AsyncGPUReadback.RequestIntoNativeSlice request
- Invalid Excluded platform behavior on QualitySettings API
- Read/Write error is thrown when making an AsyncGPUReadback request to a Native Array the second time
- The Package Manager gives inconsistent search results and shows errors in the Console when searching by publisher name
- [Player Settings] [Common] [Rendering] - Lightmap Encoding should be changed per build profile and not globally
Resolution Note (2020.2.X):
This is an edge case which is, unfortunately, very difficult to fix in the current system.