Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
2021.3.47f1
2022.3.56f1
6000.0.34f1
6000.1.0b2
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-92938
Regression
No
Crash on TransferField_NonArray<YAMLRead,Converter_String> when opening a specific project
How to reproduce:
1. Open the attached “IN-91766.zip” project
2. Observe the crash
Reproducible in: 2021.3.47f1, 2022.3.56f1, 6000.0.34f1, 6000.1.0b2
Reproducible on: Windows 11
Not reproducible on: No other environments tested
First few lines of stacktrace:
{noformat}0x00007ff60ad05276 (Unity) TransferField_NonArray<YAMLRead,Converter_String>
0x00007ff60ac7b346 (Unity) ExecuteSerializationCommands<ConfigSettingsRead>
0x00007ff60acf247e (Unity) YAMLRead::Transfer<ManagedObjectTransferer>
0x00007ff60ad2736a (Unity) Transfer_ManagedObject<YAMLRead,0>
0x00007ff60ac7b466 (Unity) ExecuteSerializationCommands<JSONRead>
0x00007ff60ac95c13 (Unity) <lambda_d4d95dac1825d5ffc4e385f6ea8312c8>::operator(){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
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- "Add Component" button overlaps the Volume component UI when creating a new Volume Profile in a wide Inspector on high-DPI scaling
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
- UI counter displays incorrect collectible count when using "Remaining_Collectibles_UI" Prefab in "Get Started With Unity" template
- Camera Output Texture does not revert back to previously set Render Texture when camera selection in UI Builder canvas background is changed
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.