Search Issue Tracker
Fixed
Fixed in 2021.3.19f1, 2022.2.0a3
Votes
0
Found in
2021.3.16f1
2022.1.24f1
2022.2.0a2
Issue ID
UUM-21911
Regression
Yes
Crash on scripting_cpp_string_for when opening the project
Reproduction steps:
1. Open the attached “CrashRepro” project
Expected result: The project opens
Actual result: Unity Editor crashes
Reproducible with: 2021.2.0a1, 2021.2.19f1, 2021.3.16f1, 2022.1.24f1, 2022.2.0a1, 2022.2.0a2
Not reproducible with: 2020.3.43f1, 2021.1.28f1, 2022.2.0a3, 2022.2.2f1, 2023.1.0a24
Reproducible on: Windows 11 22H2
First lines of the stack trace:
{noformat}0x00007ff6189ee9ce (Unity) scripting_cpp_string_for
0x00007ff61a63ad75 (Unity) ExtractAllClassesThatAreUserExtendedScripts
0x00007ff61a63b664 (Unity) PluginImporter::GenerateAssetData
0x00007ff619d5de7e (Unity) ImportToObjects
0x00007ff619d5cde3 (Unity) ImportAsset{noformat}
Note: Reimport the project on every Unity version
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Particle System only collides with one Terrain Collider at a time when Collision Type is set to 'World'
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
Add comment