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.
Comments (1)
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
shubhamswaraj2021
Aug 18, 2020 16:15
good one <a href="https://www.lyricsauto.com">lyricsauto</a>