Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.5.0f3
Issue ID
858781
Regression
No
Index out of range exception is thrown in Windows Development builds
Reproduction steps:
1. Open the attached project in unity
2. Build the project to Windows (Development build, x84_64)
3. Run the executable
Result: the console throws out "index out of range exception", when it's clearly not
There is a possible workaround:
1. Open the "NewBehaviourScript.cs"
2. Change the whole update function to
mArray2[4, 4] = 1;
mArray2[4, 3] = 1;
3. Then the error is not thrown, even though the code does exactly the same thing
Reproducible on: 5.3.7p1, 5.4.3p3, 5.5.0f3, 5.6.0b1
------------------------------------------
This issue will be addressed after new scripting runtime will be released (https://unity3d.com/unity/roadmap).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Add comment