Search Issue Tracker
Fixed in 0.4.4-preview.2
Votes
0
Found in [Package]
0.4.3-Preview.1
Issue ID
1388611
Regression
No
Memory Profiler fragmentation compare view shows managed memory as "Modified" when it should show it as deallocated
1) Load both attached memory captures into Unity (I am using Memory Profiler 0.4.2-preview.1)
2) Open Memory Profiler
3) Load the earlier capture (ending in "518") as capture A
4) Load the later capture (ending in "162") as capture B
5) Go to the compare snapshots Fragmentation view
6) Make sure the Row Size is set to 8 MB
7) scroll to the managed memory just past the address "0x0000011EF800000"
Observed result
There is a 12.5MB large yellow "Modified" chunk of memory for the object CompatOctree[1638400]
Expected result
This 12.5MB is red. This allocation exists in capture A but is empty in capture B as it was garbage collected.
Also note that swapping the snapshots so that A is B and B is A is not immediately reflected in the Fragmentation view but only when going to a different view and coming back to it, only then all the red area's are green and vise versa.
Expected result: swapping the snapshots positions should be reflected immediately.
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 process is hidden in macOS dock
- Shader warnings are being thrown after building Mixed Reality Template
- Error is thrown when entering play mode with build profiles docked and standalone profiler open
- The Player hangs when activating another maximized application
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
Resolution Note (fix version 0.4.4-preview.2):
Fixed in: 0.4.4-preview.2