Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.0.0
Issue ID
PROFB-56
Regression
Yes
IndexOutOfRangeException errors are thrown in the Console when expanding UnityEditor.EditorWindow Managed Field in the Memory Profiler
Reproduction steps:
- Open the attached “Repro.zip” project
- Open Memory Profiler (Window > Analysis > Memory Profiler)
- Select the “Blank_2023-1_2022-11-21_08-37-42” snapshot
- Select the “Unity Objects” Tab and select “GameView RT” in the list (RenderTexture > GameViewRT)
- Expand “UnityEditor.GameView “““ in the “Referenced By” category on the right and select the first item from the top
- Expand any of the Managed Fields in the list under the Selection Details category
- Observe the Console window
Expected result: No errors in the Console window
Actual result: “IndexOutOfRangeException: Index was outside the bounds of the array” errors are being thrown in the Console window
Reproducible with: 1.0.0-pre.1, 1.0.0 (2023.1.0a20, 2023.1.0a22)
Not reproducible with: 0.7.1-preview.1 (2020.3.42f1, 2021.3.15f1, 2022.1.24f1), 1.0.0-pre.1, 1.0.0 (2022.2.1f1, 2023.1.0a19)
Reproducible on: Windows 10 (21H2)
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:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-20795
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-20795