Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
7
Found in
2019.2.0a1
2019.4
2019.4.0f1
2020.1
2020.2
Issue ID
1257220
Regression
Yes
Editor crashes on MemoryManager::GetAllocator when selecting NavMeshAgent Component in the Inspector window
Reproduction steps:
1. Open the user's attached "Zombie.zip" project
2. Load the "TeddyLab" scene
3. Select "Enemy" GameObject in the Hierarchy window
4. Click on NavMeshAgent Component in the Inspector window
-- Observe the crash
Reproducible with: 2019.2.0a1, 2019.2.21f1 2019.4.0f1, 2020.1.0b14, 2020.2.0a16
Not reproducible with: 2018.4.23f1, 2019.1.14f1
Note: in some version, the crash occurs when selecting a GameObject with NavMeshAgent Component
First lines of the stack trace:
0x00007ff7b57d9ecc (Unity) MemoryManager::Allocate
0x00007ff7b57ef51c (Unity) malloc_internal
0x00007ff7b4d434ae (Unity) core::StringStorageDefault<char>::allocate
0x00007ff7b6b04790 (Unity) NavMesh_CUSTOM_GetSettingsNameFromID
0x000001738011153e (Mono JIT Code) (wrapper managed-to-native) UnityEngine.AI.NavMesh:GetSettingsNameFromID (int)
<...>
-
adriant
Jul 29, 2020 12:33
Quick workaround: To correct the issue in the project and avoid the crash please open the file ProjectSettings\NavMeshAreas.asset in a text editor and make sure that the properties "m_Settings:" and "m_SettingNames:" have the same number of items declared under them.
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
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Camera.WorldToScreenPoint is producing different behavior with dynamic resolution
- Gray color does not equal gray when comparing Color.gray and Color.gray
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b2
Quick workaround:
To correct the issue in the project please open the file ProjectSettings\NavMeshAreas.asset in a text editor and make sure that the properties "m_Settings:" and "m_SettingNames:" have the same number of items declared under them.
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.6f1.4510
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.11f1