Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.1.6f1
Issue ID
1068736
Regression
No
NavMeshPath::GetCornersNonAlloc generate 32B of Garbage per frame
To reproduce:
1. Open the attached project (GetCornersGarbage_Test.zip)
2. Open the Sample Scene
3. Enter Play mode
4. Open the Profiler, search for GetCornersNonAlloc and see that the method allocates 32B
Expected: NavMeshPath::GetCornersNonAlloc doesn't allocate anything
Reproduced in 2017.3.2f1, 2017.4.9f1, 2018.1.6f1, 2018.1.9f1, 2018.2.3f1, 2018.3.0a8
---
Issue not reproducible: By enabling the option for "Deep profile" we could verify that GetCornersNonAlloc() does not allocate any GC memory, as expected. The GC allocation is made by the `path` property of the NavMeshAgent for which we do not guarantee GC-free allocation.
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
shubhamswaraj2021
Aug 18, 2020 16:15
good one <a href="https://www.lyricsauto.com">lyricsauto</a>