Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.40f1
6000.1.0b8
6000.2.0a5
6000.3.0a1
Issue ID
UUM-98513
Regression
No
"EndLayoutGroup: BeginLayoutGroup must be called first" is thrown when selecting the wrong executable for the browser and then the right one
How to reproduce:
1. Make sure the Web module is installed and create a new project
2. Open the Build Profiles and switch to the Web
3. In the Web settings, choose a not default browser
4. Browse the path to the browser and select the random executable
5. Click "Browse" again and select the right browser executable
6. Click "Open" and observe the Console
Expected results: No errors are thrown
Actual results: "EndLayoutGroup: BeginLayoutGroup must be called first." error is thrown
Reproducible with: 6000.0.40f1, 6000.1.0b8, 6000.2.0a5
Reproducible on: Windows 11, macOS Sequoia 15.3 (M1)
Notes:
- Reproducible in the empty project
- Bug is not reproducible when switching to the default browser and back to any other with the previously selected .exe
- Sometimes the bug is reproducible by selecting the right executable
- Canceling the selection might trigger an error
Full error:
EndLayoutGroup: BeginLayoutGroup must be called first.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /Users/bokken/build/output/unity/unity/Modules/IMGUI/GUIUtility.cs:219)
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
I read the linked Slack thread. Looked at the repro. It still seems like a specific use case issue and not a systemic IMGUI-wide issue to me. Open to change my mind and take back this bug if new information surfaces. We don't have the capacity to investigate all use cases where there are Begin/EndLayoutGroup mismatch error to verify that they are in-fact IMGUI bugs. We're also reluctant to make changes to how Begin/EndLayoutGroup handle such errors because the potential for larger scale regressions is not worth the risk.