Search Issue Tracker
Duplicate
Votes
0
Found in
2020.2.0a13
2020.3.5f1
2021.1
Issue ID
1332120
Regression
Yes
'Retrieving array element that was out of bounds' error is thrown on deleting a Reorderable List middle element via 'Delete' key
How to reproduce:
1. Open user-submitted project (DeleteElementArray.zip)
2. Open the SampleScene
3. Select Array GameObject
4. Delete Element 1 from the list of integers by selecting it and pressing the 'Delete' key
5. See the Console window
Expected result: no errors are thrown
Actual result: 'Retrieving array element that was out of bounds' error is thrown
Reproducible with: 2020.2.0a13, 2020.3.7f1, 2021.1.0a1, 2021.1.0a7
Not reproducible with: 2018.4.33f1, 2019.4.25f1, 2020.2.0a12, 2021.1.0a8, 2021.1.5f1, 2021.2.0a1, 2021.2.0a15
-
Resolution Note:
Fixed in 2021.1.0a8
-
chadfranklin47
Aug 30, 2022 18:21
I am getting this error on Unity 2021.3.8 LTS with UnityEditorInternal.ReorderableList. Would be nice to get a fix there also.
-
Garfield583
May 07, 2022 09:03
I having the same issuses with the TerrainTool from Unity-Build-In packages, I using Unity Version 2021.3.1f1and my solution is:
Add the following two lines in the method from the FilterStackView class found in TerrainTool's FilterStackView.cs:
--------------------------------------------------------------------------------------------
private Filter GetFilterAtIndex(int index)
{
// Add these next two lines in this Methods
if (index >= m_FiltersProperty.arraySize)
return null;
return m_FiltersProperty.GetArrayElementAtIndex(index).objectReferenceValue as Filter;
}
---------------------------------------------------------------------------------------------
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1260899