Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.1.10f1
Issue ID
UUM-9781
Regression
No
A Native Collection memory leak error doesn't have hyperlinked text to the referenced C# script
Reproduction steps:
1. Open the user's attached project
2. Open Assets > MeshMoxie > Scenes > MeshMoxie DemoScene.unity
3. Observe the Console window
Expected result: The Native Collection error has a hyperlinked text to the referenced C# script
Actual result: The Native Collection error doesn't have hyperlinked text to the referenced C# script
Reproducible with: 2021.3.6f1, 2022.1.9f1
Couldn't test with: 2020.3.37f1 (couldn't resolve console errors), 2022.2.0b1, 2023.1.0a3 (crash when opening the project)
Reproducible on: Windows 10
Error:
A Native Collection has not been disposed, resulting in a memory leak. Allocated from:
UnityEngine.Mesh:AllocateWritableMeshData(Int32)
Builders.MeshDataProvider:AllocateMeshData(Int32) (at Assets\\Builders\\MeshDataProvider.cs:29)
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 Scrollbar becomes unusable when adding Elements to the List
- "One or more data file missing for baking set NewScene Baking Set. Cannot load shared data." error in Player when a specific project is built
- Choosing new HDR Colour using RGB values breaks colour on Intensity Selectors
- Rendering/Decal Layer Mask options are different inside Prefab Mode and outside Prefab Mode when the project is upgraded to Unity 6
- Incorrect Realtime GI Light Probes baking when more than one Light Probe Group is used and "Baked Global Illumination" is enabled
Resolution Note:
There are no fixes planned for this Bug