Search Issue Tracker
Fixed in 1.0.0-pre.1
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1419214
Regression
Yes
[Memory Profiler] NullReferenceException error is thrown when expanding/shrinking a drop-down row in Memory Profiler Summary tab
Reproduction steps:
1. Open the attached Unity project "MemoryProfilerIssue.zip"
2. Open the Memory Profiler window (Window > Analysis > Memory Profiler)
3. In the Memory Profiler press the "Capture New Snapshot" button and open the snapshot
4. Then navigate to Summary > Filters > Data Type > Right Click and press on Group
5. Try expanding and shrinking the rows in the table
6. Observe that the rows disappear in the table
7. Go back to the Editor and observe the errors thrown in the Console window
Expected result: No errors are thrown in the Console window, the rows of the Table filter in Memory Profiler do not disappear
Actual result: "NullReferenceException: Object reference not set to an instance of an object" error is thrown in the Console window and Table filter data disappears when expanding and shrinking rows in Memory Profiler
Reproducible with: 0.6.0-preview.1 (2019.4.38f1, 2020.3.33f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11)
Not reproducible with: 0.5.0-preview.1, 0.5.1-preview.1 (2019.4.38f1, 2020.3.33f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.0.0-pre.1):
The table UI in Memory Profiler package has been redesigned in the 1.0.0-pre.1 version and the issue is no longer reproducible.