Search Issue Tracker
Fixed in 0.4.4-Preview.1
Votes
0
Found in [Package]
0.4.3-Preview.1
Issue ID
1393878
Regression
No
[Memory Profiler] Memory Profiler supposedly captured a 0.5 GB big string object
How to Reproduce:
1. Open an empty Project, install the Memory Profiler and Import the attached snapshot file
2. Open the snapshot
Expected: The Managed Memory breakdown's "Objects" metric is smaller than the Memory Usage breakdown's "Managed Heap" "in Use" metric
Actual: The Managed Memory breakdown's "Objects" metric is bigger than even the Memory Usage breakdown's "Managed Heap" "Reserved" metric
3. Find the System.String item in the Tree Map and select it
Expected: The table underneath the Tree Map gets filtered to a list of string Objects
Actual: An ArgumentOutOfRangeException with the message "Attempted to read outside of binary buffer." is thrown and the table only shows a broken first line
Also: The Tree Map item for System.String shows that 0.52 GB of memory is supposedly used for String objects. Note that in this snapshot, this is down to an invalid object that is interpreted as a string.
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.4-Preview.1):
Fixed in: Memory Profiler 0.4.4-preview.2