Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.26f1
Issue ID
UUM-37758
Regression
No
Crash on Walk when opening specific project
Reproduction steps:
1. Open the attached project “CrashRepro“
Expected result: Project opens
Actual result: Editor crashes
Reproducible with: 2021.3.26f1, 2022.1.24f1
Not reproducible with: 2022.2.0a1, 2022.3.0f1, 2023.1.0b19, 2023.2.0a18
Reproducible on: Windows 10
First few lines of stack trace:
{noformat}0x00007ff6581d31f2 (Unity) Walk
0x00007ff6581d32a8 (Unity) Walk
0x00007ff6581d18bf (Unity) SafeBinaryRead::BeginTransfer
0x00007ff657a8a583 (Unity) EditorExtension::Transfer<SafeBinaryRead>
0x00007ff657a768f2 (Unity) NamedObject::Transfer<SafeBinaryRead>{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
- UI Toolkit World UI Text Field unfocuses immediately when clicking on it using XR Controller
- Crash on CallWindowProcW when entering Play mode for the second time and running the Editor in the background while using System.Windows.Forms functions
- 2D Freeform Light shadows disappear when light center is offset from shape bounds
- Crash on MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
- Crash on CollectAllSceneManagerAndObjectIDs when opening a specific Scene
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 (2021.3.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.