Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.69f1
6000.3.11f1
6000.4.0b11
6000.5.0a8
6000.6.0a1
Issue ID
UUM-136209
Regression
No
"GUI Error" and "ArgumentException" errors are thrown when IMGUI Debugger windows is docked next to the window it is inspecting
Steps to reproduce:
- Create a new project using Universal 3D template
- Go to Window > Analysis > IMGUI Debugger
- Switch the "Inspected View:" dropdown to "Hierarchy"
- From the left-hand panel, select any entry under Instructions
- Dock the IMGUI Debugger window next to the Hierarchy window
- Observe the Console
Actual results: "GUI Error: Invalid GUILayout state in GUIViewDebuggerWindow view. Verify that all layout Begin/End calls match" and "ArgumentException: Getting control 2's position in a group with only 2 controls when doing repaint" errors
Expected results: No errors
Reproducible with versions: 2023.1.0b1, 6000.0.69f1, 6000.3.11f1, 6000.4.0b11, 6000.5.0a8
Tested on (OS): Windows 11
Notes:
- Not specific to the Hierarchy window; it occurs with any IMGUI window that is selected as the inspected view and then docked next to the IMGUI Debugger
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.
Resolution Note (6000.6.X):
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.