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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment