Search Issue Tracker
In Progress
Votes
0
Found in [Package]
0.5.0-preview.1
0.5.1-preview.1
0.6.0-preview.1
0.7.0-preview.1
0.7.0-preview.2
0.7.1-preview.1
0.7.1-preview.2
1.0.0-pre.1
1.0.0-pre.2
1.0.0-pre.3
1.0.0
1.0.1
1.0.2
1.0.3
1.1.0-exp.1
1.1.0-pre.1
1.1.0-exp.2
1.1.0-pre.2
1.1.0-pre.3
1.1.0
1.1.1
1.1.2
1.1.3
1.1.4
Issue ID
PROFB-353
Regression
No
Memory Profiler doesn't find references to NativeArrays smaller than 16B (or 24B on x64)
Steps to reproduce:
- Open attatched snapshot in the Memory Profiler window (in the package com.unity.memoryprofiler), and navigate to All Of Memory page
- Search for ReferenceHolder and select the instance named "Root"
- Scroll down to the Managed Fields inspector and find the m_Data field as well as the m_DataPtr field
Actual results: They report that the fields are pointers at a Native Region.
Expected results: They report that the fields are pointers at a Native Allocation under named root UnsafeUtility.Malloc(Persistent).
Reproducible with versions: 0.5.0-preview.1, 1.0.0, 1.1.6 and Unity 2022.3.65f1
Not reproducible with versions: 0.4.4-preview.2 (because it doesn't provide that info at all, not because it was working) or captures made from Unity before and Unity 2022.2 (because the reported allocation size would include the entire block size, not because the Memory Profiler package logic was right).
Can’t test with versions:
Tested on (OS): Win11
Notes:
- The array in the snapshot is 20B in size but it comes from a Debug build of Unity where the min size of a NativeArray that would be findable would have to be 32B
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment