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
- Scene view audio toggle doesn't work after disabling and enabling audio source component with audio random container
- Pitch changes while paused messes up scheduling of the audio random container
- Crash on detail::ComputeShaderSnippetKey when entering the Play mode
- Unable to interact with Material Inspector window when creating a new Material and renaming it
- Shadow artifact is cast onto GameObjects in the Scene view when the Scene view lighting is disabled
Resolution Note (fix version 0.4.4-Preview.1):
Fixed in: Memory Profiler 0.4.4-preview.2