Search Issue Tracker
Fixed
Fixed in 1.0.0
Votes
0
Found in [Package]
1.0.0-pre.6
Issue ID
NCCBUG-139
Regression
No
Native Collection memory leak error is thrown when spawning GameObject with NetworkAnimator twice
How to reproduce:
1. Open the attached project (Bug Sample Project.zip)
2. Open scene Scenes/Login Screen
3. Press the Play button
4. Observe the Console for 10-20 seconds
Expected result: no Native Collection error is thrown
Actual result: "A Native Collection has not been disposed, resulting in a memory leak." is thrown 10-20 seconds after respawning GameObject
Reproducible with: 1.0.0-pre.2, 1.0.0-pre.6 (2020.3.31f1, 2021.2.16f1, 2022.1.0b12, 2022.2.0a8)
Could not test with: 2019.4.36f1 (Netcode not supported)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
- Unity Perforce Integration: VCS Connection Active State Fails via CLI with Valid Inputs
Add comment