Search Issue Tracker
Fixed in 2022.2.3f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a21
Votes
0
Found in
2022.2.0b6
2023.1.0a8
Issue ID
UUM-12869
Regression
Yes
"Out of bounds" error is thrown sometimes when deleting an element of two arrays with unique sizes
How to reproduce:
1. Open the attached “case IN-14156” project
2. Open the “SampleScene” Scene
3. Multi-select “Test_1” and “Test_2” GameObjects in the Hierarchy
4. Select one of the array elements by clicking on the element’s name area in the Inspector
5. Delete the selected element
Expected result: Array element is deleted, and a complete array is copied to all other selected objects
Actual result: In 1 of 5 cases, an array element is deleted and an array is copied, but with “Retrieving array element that was out of bounds” errors thrown by the “UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)” method
Reproducible with: 2022.2.0a9, 2022.2.0b6, 2023.1.0a8
Not reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0a8
Reproduced on: macOS 12.3 (Intel)
Note:
- Issue mainly reproduces when at selection clicking the element name area
- In some versions, nothing is deleted or copied, but additionally “NullReferenceException: Object reference not set to an instance of an object” error is thrown
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 2023.1):
Fixed in 2023.1.0a21
Resolution Note (fix version 2022.2):
Fixed in 2022.2.3f1