Search Issue Tracker
Fixed
Fixed in 2022.3.40f1
Votes
0
Found in
2022.3.38f1
Issue ID
UUM-75917
Regression
Yes
"ArgumentOutOfRangeException" error appears when selecting multiple GameObjects with Sprite Renderer Component attached and changing the script
How to reproduce:
1. Open the “Test2023_2_20f1“ project
2. Open the “SampleScene“
3. In the Hierarchy, select all “40x40_Circle_0” GameObjects
4. Open the “TestScript” in the Assets folder
5. Change the script to trigger the compilation process (e.g. add {{Debug.Log("Test")}})
6. Observe the Console
Expected result: No error is thrown
Actual result: The “ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection” error is thrown
Reproducible in: 2022.3.30f1, 2022.3.38f1, 2023.2.20f1
Not reproducible in: 2021.3.40f1, 2022.3.29f1, 6000.0.11f1
Fixed in: 6000.0.0f1
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Notes:
- The full error is provided in the internal comments
- In the first few versions prior to the Fixed In one, the error is “NullReferenceException: Object reference not set to an instance of an object”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Add comment