Search Issue Tracker
Fixed
Fixed in 6000.3.0b3, 6000.4.0a1
Votes
0
Found in
6000.3.0a1
6000.3.0a5
6000.4.0a1
Issue ID
UUM-116049
Regression
Yes
[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: 6000.2.0a10
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
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
- Standalone Profiler stays in Dark Theme after switching Editor theme to Light on Ubuntu
- Inconsistency in capitalisation and styling across various nodes and block in VFX Graph
- Package Manager Select all keyboard shortcut selects all packages even if they’re not visible to the user when the Package Manager has no search results and the shortcut is pressed
Add comment