Search Issue Tracker
Not Reproducible
Under Consideration for 2022.3.X, 6000.0.X, 6000.3.X, 6000.4.X
In Progress in 6000.5.X
Votes
3
Found in
2021.3.1f1
2022.1.0b14
2022.2.0a9
6000.0.37f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-2955
Regression
No
Memory leak in NavmeshAgent.SetDestination method when multiple agents are in the same position
How to reproduce:
1. Open the attached "case_1404634" project
2. Enter the Play Mode in the "UnloadScene" Scene
3. Open the "Window -> Analysis -> Memory Profiler" window from the menu
4. Capture a Snapshot
5. Enter the Play Mode in the "SampleScene" Scene for 10 minutes
6. Repeat the 2-4 steps to fully unload Assets from the "SampleScene" Scene
7. Select the captured Snapshots in the "Compare Snapshots" section
8. Select the "Diff All Native Allocations" Table view
9. Apply the following filters to the Table view:
- "Root Reference" column is "No Root"
- "Diff" column is "New"
- "Sort" column is "Descending"
10. Observe the Table view
Expected result: No new "No Root" memory is observed in the filtered Table view
Actual result: More than 5 megabytes of memory is leaked in total of 15 thousand leaked memory fragments
Reproducible with: 2019.4.37f1, 2020.3.32f1, 2021.2.18f1, 2021.3.1f1, 2022.1.0b14, 2022.2.0a9
Note: Related to https://forum.unity.com/threads/memory-leak-in-navmeshagent-setdestination-if-multiple-agents-in-the-same-position.1242958/
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
- 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
Resolution Note:
It's not immediately obvious that we're leaking anything in navigation. According to the route memory labels we're not. Memory is growing a bit in 6000.3 but i again can't see how it's attributed to nav.
There is an awful lot of UIElements throughout the memory debugger. I looked at some of the bigger unrooted allocations and they weren't coming from Nav.
I don't know what to do here, i don't think it's worth spending too much time on unless it's provably nav.
Resolution Note:
It's not immediately obvious that we're leaking anything in navigation. According to the route memory labels we're not. Memory is growing a bit in 6000.3 but i again can't see how it's attributed to nav.
There is an awful lot of UIElements throughout the memory debugger. I looked at some of the bigger unrooted allocations and they weren't coming from Nav.
I don't know what to do here, i don't think it's worth spending too much time on unless it's provably nav.