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.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment