Search Issue Tracker
Fixed
Fixed in 2.0.9
Votes
0
Found in [Package]
1.1.5
2.0.1
Issue ID
NAVB-96
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)
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
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
- Advanced dropdown stops applying the Search Filter while the search text remains after clicking the header back Button during a Search
- SRP Batcher ignores ShadowCaster pass when Fallback shader has mismatched CBUFFER layout
- Crash on PolynomialCurve::BuildCurve when calling ParticleSystemRenderer.SetMeshes() with an AnimationCurve containing 9 or more keys
- NullReferenceException is thrown when a Graph Toolkit graph is "saved as"
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.