Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0b2
Issue ID
989622
Regression
No
PackedMemorySnapshot: NativeArray memory is not captured in it
To reproduce:
1) Open attached project and scene
2) Play it
3) Click Bugreport->Open Test Code Window
4) Click "Capture Memory 'Editor'" Button
Expected: It reports a Native Array (you can see with Detailed Memory Snapshot made with profiler that it exists)
Actual: It reports nothing
Reproduced in 2018.1.0b2
The Detailed Memory view functions are on a different system than the Packed Memory snapshot when it comes to collected metrics. The Packed Memory Snapshot was not designed to directly collect native memory allocations instead it will only collect Types that inherit from Object (eg: GameObjects). While we will not be adding support for collecting native allocations to the current snapshot capture functionality we are working on a new system that will not have this restriction.
Comments (1)
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
- Typos in High Definition 3D sample tutorials
- “Handles.Repaint called outside an editor OnGUI" error is thrown in the Console when creating a new Tile Palette from the Tile Palette Overlay in Scene view
- Shader Graph window icon is blurry and low quality when the Shader Graph is created using the Universal 2D template
- “Export HDRP Sky to Image” command error message does not indicate that Game view must be visible
- Adaptive Performance Settings Framerate field doesn't display the "supported without VSync" warning, when the field is collapsed in Build Profiles
Peter77
Jun 11, 2018 17:02
Related forum thread:
https://forum.unity.com/threads/case-989622-packedmemorysnapshot-nativearray-memory-missing-allegedly-fixed-in-2018-2.535620/