Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
0.6.0-preview.1
0.7.1-preview.1
Issue ID
PROFB-84
Regression
No
Error "IndexOutOfRangeException: Index was outside the bounds of the array" is thrown when selecting from the "Objects and Allocations" list in Memory Profiler
How to reproduce:
1. Open the project “IN_16812”
2. Press Window → Analysis → Memory Profiler
3. Click on any Snapshot
4. Go to Objects and Allocations
5. Press Type → Match and type “PlayerController”
6. Select different rows
Expected result: no error in the Console
Actual result: error in the Console
Reproducible with: 0.6.0-preview.1, 0.7.1-preview.1 (2020.3.40f1, 2021.3.11f1, 2022.2.0b9)
Not reproducible with: 1.0.0 (2022.2.0b9, 2023.1.0a12) (checked in Player Controller row in “Unity Objects”)
Fixed in: 1.0.0
Reproducible on: Windows 10 Pro
Error first lines:
IndexOutOfRangeException: Index was outside the bounds of the array.
Unity.MemoryProfiler.Editor.UI.ManagedObjectInspector.FindNativeAllocationOrRegion (Unity.MemoryProfiler.Editor.CachedSnapshot cs, System.UInt64 pointer, Unity.MemoryProfiler.Editor.UI.ManagedObjectInspectorItem childItem, System.String value, System.String nativeFieldName, System.String nativeAllocationTypeName) (at Library/PackageCache/com.unity.memoryprofiler@0.7.1-preview.1/Editor/UI/PathsToRoot/ManagedObjectInspector.cs:414)
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
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
Resolution Note:
Fixed in 1.0.0
As a workaround - Open the Snapshot in Unity 2022.2 in an empty project with Memory Profiler 1.0.0