Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X
Votes
1
Found in
2020.3.34f1
2021.3.1f1
2022.1.0f1
2022.2.0a11
Issue ID
UUM-3574
Regression
No
Random-write to UAV texture from shadowcaster shader causes GPU hang when filtering Scene Hierarchy objects
How to reproduce:
1. Open the user attached project
2. Open Assets/TestAssets/SampleScene scene
3. Search/filter the scene Hierarchy
Reproducible with: 2020.3.34f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11
Not reproducible with: 2019.4.38f1 due to errors running the shader in editor
Note: Typing random letters will not crash the editor, you have to search/filter
First lines of stack trace:
UnityEngine.StackTraceUtility:ExtractStackTrace ()
UnityEditor.Handles:DrawCameraImpl (UnityEngine.Rect,UnityEngine.Camera,UnityEditor.DrawCameraMode,bool,UnityEditor.DrawGridParameters,bool,bool)
UnityEditor.Handles:DrawCamera (UnityEngine.Rect,UnityEngine.Camera,UnityEditor.DrawCameraMode,bool)
UnityEditor.SceneView:RenderFilteredScene (UnityEngine.Rect)
UnityEditor.SceneView:DoDrawCamera (UnityEngine.Rect,UnityEngine.Rect,bool&)
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
This issue is specific to a user's custom shader, which accesses the unity_WorldToShadow shader variable before it is set and uses it in such a way as to cause an infinite loop.
Resolution Note (2022.2.X):
This issue is specific to a user's custom shader, which accesses the unity_WorldToShadow shader variable before it is set and uses it in such a way as to cause an infinite loop.
Resolution Note (2022.1.X):
This issue is specific to a user's custom shader, which accesses the unity_WorldToShadow shader variable before it is set and uses it in such a way as to cause an infinite loop.
Resolution Note (2021.3.X):
This issue is specific to a user's custom shader, which accesses the unity_WorldToShadow shader variable before it is set and uses it in such a way as to cause an infinite loop.
Resolution Note (2020.3.X):
This issue is specific to a user's custom shader, which accesses the unity_WorldToShadow shader variable before it is set and uses it in such a way as to cause an infinite loop.
Resolution Note:
This issue is specific to a user's custom shader, which accesses the unity_WorldToShadow shader variable before it is set and uses it in such a way as to cause an infinite loop.
Resolution Note:
This issue is specific to a user's custom shader, which accesses the unity_WorldToShadow shader variable before it is set and uses it in such a way as to cause an infinite loop.