Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0b10
2019.4
2019.4.1f1
2020.1
2020.2
Issue ID
1259684
Regression
Yes
[Memory Profiler] Memory Profiler window fails to show memory blocks and an error is thrown
Steps to reproduce:
1. Open the project in user's attached link "https://bitbucket.org/Unity-Technologies/memoryprofiler/downloads/"
2. In the top menu bar Navigate to Window->MemoryProfiler
3. Press "Take Snapshot"
4. Notice the errors in the console and the MemoryProfiler window empty
Expected results: Memory Snapshot is captured
Actual results: Error is thrown when capturing Memory Snapshot "IndexOutOfRangeException: Index was outside the bounds of the array."
Reproducible with: 2019.3.0b10, 2019.4.3f1, 2020.1.0b14, 2020.2.0a17
Not Reproducible with: 2018.4.23f1, 2019.3.0b9
Note: To correctly reproduce the issue all the steps need to follow every time the project is opened. If a Memory Snapshot window is brought up when the project is opened the issue might reproduce or not reproduce in some Unity version
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Thank you for reporting this issue. The Bitbucket Memory Profiler is no longer supported. Please use the Memory Profiler package, available in the Unity Package Manager.