Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2021.2.0a18
2022.1
Issue ID
1349827
Regression
Yes
[Memory Profiler] [Mono Upgrade] Snapshot displays <uninitialized type> entries
How to reproduce:
1. Open the attached "case_1349827.zip" project
2. Select Window/Analysis/Memory Profiler and Capture the Snapshot
3. Set taken Snapshot display type as Table/All Managed Objects
4. Click on Index and select Sort Ascending
5. Observe the first entries
Expected result: there aren't <uninitialized type> entries
Actual result: there are <uninitialized type> entries
Reproducible with: 2021.2.0a18, 2021.2.0b5, 2022.1.0a4
Not reproducible with: 2019.4.29f1, 2020.3.15f1, 2021.1.16f1, 2021.2.0a17
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 2022.1):
Fixed issue where not all GC handles were being released on domain unload.
Fixed in: 2022.1.0a12.1604
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b16