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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2022.1.X):
There are no fixes planned for this Bug