Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.0b4
2019.4
2019.4.5f1
2020.1
2020.2
Issue ID
1266540
Regression
Yes
Memory Profiler does not display the memory used by the elements of jagged arrays
How to reproduce:
1. Open the attached project "1266540.zip"
2. Open the "Test" Scene
3. Enter the Play Mode
4. Click "Capture Player" in the Memory Profiler window and open captured snapshot
5. Right-click on "Value" column, select "Match" and enter "0101JaggedArrayElementText" to the input field
Expected result: table row containing the text "0101JaggedArrayElementText" appears
Actual result: table row containing the text "0101JaggedArrayElementText" is not found
Reproducible with: 2019.3.0b4 (0.2.5-preview.1), 2019.4.6f1 (0.2.5-preview.1), 2020.1.1f1 (0.2.5-preview.1), 2020.2.0a20 (0.2.5-preview.1)
Does not reproduce with: 2018.4.26f1 (0.2.5-preview.1), 2019.3.0b3 (0.2.3-preview.1, 0.2.5-preview.1)
Could not test with: 0.2.2-preview.1 and older - console errors prevented from testing
Note:
- Only reproduces when using jagged arrays, but does not reproduce when using multidimensional arrays
- Reproduces with any data type (int, float, string, custom data types, etc...)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment