Search Issue Tracker
Fixed
Fixed in 1.1.0-exp.1
Votes
0
Found in [Package]
1.0.0
Issue ID
PROFB-97
Regression
Yes
[Memory Profiler] "ArgumentNullException: Value cannot be null" error when trying to open a snapshot
Steps to reproduce:
1. Open the attached “MemorySnapshotErrorBug” project
2. Open Memory Profiler by going to Window → Analysis → Memory Profiler
3. Capture New Snapshot
4. Observe the Memory Profiler and the Console
Expected result: Shows no errors and shows a summary of the snapshot in Memory Profiler
Actual result: "ArgumentNullException: Value cannot be null" error in the Console and no snapshot information in the Memory Profiler
Reproducible with: 1.0.0-pre.2 (2022.2.10f1), 1.0.0 (2022.2.0a16, 2022.2.10f1)
Not reproducible with: 0.7.1-preview.1 (2020.3.46f1, 2021.3.20f1, 2022.2.10f1), 1.0.0-pre.1 (2022.2.10f1), 1.0.0 (2023.1.0b7, 2023.2.0a5)
Could not test with: 1.0.0 (2020.3.46f1, 2021.3.20f1) (editor versions aren’t compatible with 1.0.x package version)
Reproduced on: macOS Monterey 12.2 (Intel), Windows 10
Notes:
- The issue is in both Editor and package versions combined
- Comparing snapshots gives the same actual result
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
- Crash on memcpy when opening a project that loads TSS files
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
- TextMeshPro memory leak occurs when reloading the scene using Addressables
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
Resolution Note (fix version 1.1.0-exp.1):
The errors shown no longer occur