Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.1.0b9
Issue ID
UUM-99534
Regression
No
Error "ArgumentOutOfRangeException" logged when cancelling Scene Hierarchy search by type intermittently
Steps to reproduce:
- Open any Project
- Open a Scene with 2 Cameras in it
- Navigate to Window > Rendering > Occlusion Culling
- Bake any Occlusion Settings
- In the Occlusion Window, in the Visualization panel select the "Cameras" Scene Filter
- Enter Play Mode
- In the Scene Hierarchy Search field click the x to remove any search parameters
Actual results: Errors are logged in Console
"ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: startIndex"
"UI Error: Invalid GUILayout state in SceneHierarchyWindow view. Verify that all layout Begin/End calls match"
Expected results: No errors are logged
Reproducible with versions: 6000.1.0b9
Can’t test with versions: 2022.3.60f1, 6000.0.42f1, 6000.2.0a6 (Unable to consistently reproduce the issue)
Tested on (OS): Windows 11
Notes:
- Issue is not reproducible most of the time, if someone finds working reproduction steps, please submit them
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.