Search Issue Tracker
Won't Fix
Won't Fix in 2022.1.X
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2022.1.X):
There are no fixes planned for this Bug