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.
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
- Standalone Profiler recording data with Play Mode target selection when Play Mode is not entered
- [HDRP] Assertion printed when Maximum Reflection Probe count is higher than 64 due to k_MaxCubeReflectionsOnScreen when Raytracing is enabled
- Seams are visible on the Water System when multiple tiles are used and their Surface type is set to River
- Matching Game View creates unsaved changes even though nothing to save
- AudioClips do not have path or GUID in Build Report and incorrect size is reported
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/