Search Issue Tracker
Active
Votes
0
Found in
2022.3.66f1
6000.0.56f1
6000.1.16f1
6000.2.2f1
6000.3.0a5
Issue ID
UUM-116049
Regression
No
[Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
How to reproduce:
1. Before you open a project, add the commandline option {{-enable-memoryprofiler-callstacks}} (via the three dot menu), then open it. (alternatively, when taking a snapshot from a Player, start it with that commandline option.
2. Open the Memory Profiler and take a snapshot (make sure you use a version that has MemLabel support (see comments))
3. Open the snapshot and go to the All Of Memory page.
4. Find the group of items under Native > Unity Subsystem > Unrooted > Unrooted.
Expected result: The allocations are not split up into their respective memory labels (multiple sub categories).
Actual result: The allocations are not split up by their respective memory labels.
Reproducible on: WIndows 11, Nintendo Switch
Not reproducible on: No other environment tested
Note: The commandline option was only added in 6000.3. For previous versions, the precompiler directive ENABLE_DEBUG_GFXALLOCATION_CALLSTACK_INFO must be set to 1 when compiling Unity.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
Add comment