Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2019.4
2019.4.13f1
2020.1
2020.2
2021.1
2021.2
Issue ID
1297742
Regression
No
Crash on entering Play mode when a script is calling NavMeshSurface.UpdateNavMesh()
How to reproduce:
1. Open the attached project named "NavMeshTest.zip"
2. Open the Game Scene located in Assets/Src/Scenes/Game
3. Enter Play mode. If the crash does not occur, exit and enter the Play mode a few times
Expected results: The Scene is loaded and Editor enters into Play mode
Actual results: Editor crashes when entering Play mode
Reproducible with: 2019.4.20f1, 2020.1.17f1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a4
Could not test with: 2018.4.30f1(Project breaks on downgrade)
Notes:
1. Crash usually occurs when trying to enter the Play mode for the second time
2. If line 12 in Map.cs is removed, the crash does no longer occur
3. Start(), FixedUpdate() and Update() methods were tested for the UpdateNavMesh call. The issue would reproduce in all test cases
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
- In Play Mode, an extra Sync Call is made every frame when a GameObject has a Rigidbody 2D component
- Crash on block_remove when a scene is opened in a specific project
- The GameObject with a Hinge Joint Component does not return to the initial position when the Use Motor property is toggled off
- The construction of a specific class breaks the binding Bool references and does not allow them to be toggled on back by hand when working in the Custom Editor window
- AssetReferenceAtlasedSprite creates a copy of the Sprite during Addressables.LoadAssetAsync<TObject> which does not release when Addressables.Release is used
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a3
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b7