Editor loads for a long time when doing an Undo action in a large Shader Graph

Unity: ShaderGraph

Fixed

2023.3.X

2022.3.X

Won't Fix

2023.2.X

2023.1.X

2021.3.X

A fix for this is incoming for the next minor version (23.3).

Fixes for this issue are incoming, but we won't be backporting to the 23.1 version.

We should see an order of magnitude improvement to undo/redo times. Unfortunately, the undo/redo performance is based on the size of the graph and not the action itself. On very large graphs, we still recommend breaking them down into subgraphs where appropriate.

Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Open the "Assets/ShaderGraph.shadergraph" file
3. Move any Node in the “ShaderGraph” window
4. Perform the Undo action (macOS: command+z, Windows: ctrl+z)

Expected result: The Undo action is performed without a long Editor loading time
Actual result: Editor starts to load and completes the Undo action after several minutes

Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.15f1, 2023.2.0b11, 2023.3.0a7

Reproducible on: macOS 13.6 (M1 Max)
Not reproducible on: No other environment tested

Note: With version 2023.1.15f1 the Undo action is performed quicker compared to the other mentioned versions

Editor loads for a long time when doing an Undo action in a large Shader Graph

Unity: ShaderGraph

Fixed

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Editor loads for a long time when doing an Undo action in a large Shader Graph

Unity: ShaderGraph

Statuses

Fixed

Won't Fix

Resolution Notes

2023.2.XWon't FixA fix for this is incoming for the next minor version (23.3).

2023.1.XWon't FixFixes for this issue are incoming, but we won't be backporting to the 23.1 version.

2022.3.XFixedWe should see an order of magnitude improvement to undo/redo times. Unfortunately, the undo/redo performance is based on the size of the graph and not the action itself. On very large graphs, we still recommend breaking them down into subgraphs where appropriate.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?