Search Issue Tracker
Active
Votes
0
Found in
2021.3.37f1
Issue ID
UUM-70246
Regression
No
NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
How to reproduce:
1. Download and open the attached project
2. Open SampleScene scene
3. Open the Profiler window
4. Turn on Deep Profiling
5. Enter Play mode
6. Repeatedly press the "Add 200 NavMeshModifiers" button
7. Observe the Profiler window
Expected outcome: Memory consumption does not gradually increase
Actual outcome: Memory consumption gradually increases with each button press
Reproducible with: 2021.3.37f1, 2022.3.25f2, 2023.2.19f1, 2023.3.0b10, 6000.0.0b16
Tested on: macOS Sonoma 14.4.1 (M1 Max)
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
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not always matching search term correctly
- Crash on memcpy when opening a project that loads TSS files
James2Games
Apr 25, 2024 20:27
To be clear the memory consumption isn’t the issue. It’s problem is the time taken in OnEnable an OnDisable because they do a .contains on a list that becomes very large.