Not signed in
Copyright © 2026 Unity Technologies
Thank you for reporting a bug to Unity. We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken. We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Thank you for reporting a bug to Unity. We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken. We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Thank you for reporting a bug to Unity. We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken. We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Unity 6000.2 has reached its end of life and will not receive further updates. If you need additional fixes, please upgrade to a newer Unity version.
Cancelling: the 6000.1 version has reached its end of life. If you need additional fixes, please upgrade to a newer Unity version.
Thank you for reporting a bug to Unity. We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken. We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
2022.1 has reached end of life so the issue will be fixed in a newer version.
Unity 2021.3 has reached its end of life and will not receive further updates. If you need additional fixes, please upgrade to a newer Unity version.
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:
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/
Sign in to see your voted issues