Search Issue Tracker
By Design
Under Consideration for 2021.3.X, 2022.3.X, 2023.2.X, 2023.3.X
Votes
0
Found in
2021.3.30f1
2022.3.10f1
2023.1.15f1
2023.2.0b11
2023.3.0a7
Issue ID
UUM-52907
Regression
No
Editor hangs on Import when a specific Shader Graph is in the project
How to reproduce:
1. Open the “IN-55454_repro“ project
Expected result: The Editor opens
Actual result: The Editor hangs at Importing
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.15f1, 2023.2.0b11, 2023.3.0a7
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Note:
- Sometimes hangs on EditorApplication.Update
- Reproduces only when the “64 Connected.shadergraph“ is in the project
Comments (2)
-
NexysStormcloud
Oct 19, 2024 19:57
same issue on unity 6000.0.23f1 lts
after deleting meta file of shadergraph that causes problem, loading process continues, and game launches successfuly without any error.
-
JasonSpine
Jul 24, 2024 02:37
I've got the same problem in Unity 6000.0.11f1
Progress bar => full
Window title => Importing (iteration 2) (busy for 50s)...
Below progress bar => *.shadergraph file pathI could wait and wait and nothing happens.
This shadergraph is not so complicated.
If I go to this file in Files Explorer and change it's name. It un-hangs Unity editor. Then I change this file's name back to what it was and I can continue my work.
Shader in this file also works ok.
It doesn't happen all the time.
Usually when I save a script in Visual Studio and go back to Unity Editor.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
We've landed numerous performance improvements for large graphs. I believe the issues that were being experienced here have been addressed in recent versions. I'm closing this for now, but please reopen this issue if any problems persist.