Search Issue Tracker
Fixed in 0.4.3-preview.1
Votes
0
Found in [Package]
0.4.2-preview.1
Issue ID
1381034
Regression
No
[Memory Profiler] Memory Usage Breakdown Categories don't add up to the Total
This Bug was split in too, the other half is tracked as Case 1383114
The Top Memory usage categories add up to more than the Total on some platforms, as Unity may consider more memory as "in use/reserved" than the platform API's return for the System Used Memory Profiler Counter. This leads to confusing displays in the Memory Profiler Package where the total may have a bigger or significantly different variation between 2 snapshots than what the categories in the bar suggest would be different between the two.
This also means that the categories do not add up to the Total.
How to reproduce:
1. Open any Project
2. Install the Memory Profiler Package via Add By Name/ Add By Git URL: "com.unity.memoryprofiler"
3. Open the Memory Profiler and click Import, choose the two attached snasphots
4. Switch from Single to Compare mode and open both snapshots
5. Observe the Memory Usage Overview > Memory Usage bar
Expected: The Reserved of all Categories added up together is equal to the total for each corresponding snapshot
Actual: The Reserved of all Categories added up together is more than the total for each corresponding snapshot
Expected: There should be a clear reason visible in the UI for any differences in the Total
Actual: There is a difference of 0.03 GB between the two snapshots, (27MB to be precise) that can not be found in the differences of each of the breakdowns
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 0.4.3-preview.1):
Fixed in: 0.4.3-preview.1
Package version available in: 2019.4, 2020.3, 2021.2, 2022.1