Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.16f1
Issue ID
UUM-35457
Regression
No
Crash on core::StringStorageDefault<char>::assign when a prefab is dragged into the Scene view or component list
Reproduction steps:
1. Open the attached project “CrashRepro“
2. Drag “Assets/Prefabs/Visual Scripts/new_class“ Prefab into the Scene view
Expected result: “new_class“ Prefab appears in the Scene view
Actual result: Editor crashes
Reproducible with: 2022.2.0a18, 2022.2.16f1
Not reproducible with: 2023.1.0a20, 2023.1.0b12, 2023.2.0a12
Couldn’t test with: 2020.3.47f1, 2021.3.24f1, 2022.2.0a17 - “error CS0246: The type or namespace name 'MultiColumnListView' could not be found”, 2023.1.0a1-2023.1.0a19 “error CS1061: 'Editor' does not contain a definition for 'dataMode' and no accessible extension method 'dataMode' accepting a first argument of type 'Editor' could be found“
Reproducible on: Windows 10
First few lines of stack trace:
{noformat}0x00007ff7c112176b (Unity) core::StringStorageDefault<char>::assign
0x00007ff7c2fff9da (Unity) DragAndDrop::FetchDataFromDrag
0x00007ff7c2feed0e (Unity) CDropTarget::DragEnter
0x00007ff86c91bc70 (ole32) RevokeActiveObjectExt
0x00007ff86c91b98c (ole32) RevokeActiveObjectExt
0x00007ff86c8d9c1e (ole32) OleGetPackageClipboardOwner{noformat}
Note: The same issue appears when “new_class“ Prefab is dragged into the Component list of another Prefab
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
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 (2022.2.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.