Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
1
Found in
6000.0.47f1
6000.1.0f1
6000.2.0a9
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-104758
Regression
No
Crash on GeneratePropertyDiffInternal when using NodeCanvas nodes
Reproduction steps:
1. Open the attached project "CrashRepro"
2. Click on the second crate in the Hierarchy window
3. Click on the action in the NodeCanvas window
4. Copy and paste a few times
Expected result: The Action gets copied
Actual result: Editor crashes
Reproducible with: 6000.0.47f1, 6000.1.0f1, 6000.2.0a9
Couldn’t test with: 2022.3.61f1 (Package is broken)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
Step 4 can be other actions, such as adding another action, setting an action, setting string values in the node canvas, or copying and pasting seems to be the fastest way to reproduce the crash
Not a 100% reproduction rate but seems to reproduce within a few minutes
First few lines of stack trace:
{noformat}0x00007FFCA46FAAB0 (Unity) GeneratePropertyDiffInternal
0x00007FFCA46FBD17 (Unity) GeneratePropertyDiffInternal
0x00007FFCA46FA1D7 (Unity) GeneratePropertyDiff
0x00007FFCA47DBD1C (Unity) GenerateUndoAndRedoDiffs
0x00007FFCA47E8BEA (Unity) PropertyUndoManager::Flush{noformat}
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
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
- Shader Graph validation errors are not pointing to the right implementation
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.