Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X
Votes
0
Found in
2018.4
2019.4
2019.4.21f1
2020.2.0a10
Issue ID
1320023
Regression
No
Crash on core::StringStorageDefault<char>::assign when attaching a specific script to specific terrain
Title: Crash on core::StringStorageDefault<char>::assign when attaching a script to terrain that doesn't inherit a native class that can manage a script
How to reproduce:
1. Open the user's attached project from "EntrehuertasSantander.zip"
2. Open scene "SampleScene"
3. Attach script "NavMeshSurfaceTests" to "Terrain" under prefab "Cube" in Hierarchy
Reproducible with: 2018.4.33f1, 2019.4.22f1, 2020.2.0a10
Not reproducible with: 2020.2.0a11, 2020.3.1f1, 2021.1.0b12, 2021.1.0b5
First lines of stack trace:
0x00007FF7947CD18A (Unity) core::StringStorageDefault<char>::assign
0x00007FF7958CB034 (Unity) AddComponentUndoable
0x00007FF79507A843 (Unity) AddDefaultComponent
0x00007FF7956E83F6 (Unity) AddComponentMenu::AddComponentToGameObjects
0x00007FF7956EAF45 (Unity) AddComponentMenu::ExecuteOnGameObjects
0x00007FF795057A61 (Unity) MenuController::ExecuteMainMenuItemOnGameObjects
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
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
- [Android] Virtual device crashes with "Scudo ERROR: invalid chunk state when deallocating address" error in Firebase Test Lab when Optimized Frame Pacing is enabled
- Particle System does not resume when its Culling Mode is set to "Pause" or "Pause and Catch-up," and particle position simulate in world space
- "Custom Render Queue" field cannot be set above "2000" when changing it in the Inspector window using Debug mode
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a11 and onwards. Now a popup appears telling users "The script doesn't inherit a class that can manage a script."
Resolution Note (fix version 2019.4):
Fixed in 2019.4.40f1