Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
1
Found in
2019.1.0a2
Issue ID
1083410
Regression
Yes
Closing the 'Shader' dropdown menu when inspecting a Material fills the Console with !asset->IsFolderAsset() errors
How to reproduce:
1. Create a new Unity project
2. Create a new Material
3. Select the Material and in the Inspector window open and close the 'Shader' drop-down menu
Expected result: no errors appear in the Console window
Actual result: the Console window is filled with 'Assertion failed on expression: '!asset->IsFolderAsset()' UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)' errors
Reproducible with: 2019.1.0a2
Not reproducible with: 2018.2.10f1, 2018.3.0b3, 2019.1.0a1
Notes:
Reproduced on Windows 10 and MacOS
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Create and publish WebGL builds” link leads to “Sorry about that, we can't find the page you're looking for.” page
- " Suspected crash in FXC. " shader compiler errors are thrown in a new project when creating a project in Hub with a very long name but below the maximum character threshold
- Long cloud names stretch the space in Hub when the Project dropdown is opened
- OpenGLES3 Graphics API can be used with the "Linear" Color space on unsupported GPUs resulting the error spam
- [Windows] Recommended and Downloaded Learn tabs are empty and have scrollbar
Add comment