Search Issue Tracker
Fixed
Fixed in 1.0.0
Votes
4
Found in [Package]
1.0.0
Issue ID
ECSB-122
Regression
No
ObjectDisposedException and ArgumentException errors occur when selecting an entity and exiting Play Mode
How to reproduce:
1. Open the attached “nonrendering-1” project
2. Enter Play Mode
3. Open Scene view
4. Select the gray cube
5. Exit Play Mode
Expected result: No errors occur in the Console
Actual result: “ObjectDisposedException: Cannot access a disposed object.”, “You cannot call GetLast immediately after beginning a group.” and “ArgumentException: Getting control 0's position in a group with only 0 controls when doing repaint” errors repeatedly appear in the Console
Reproducible with: 1.0.0-exp.8 (2022.2.0b12, 2023.1.0a14)
Couldn’t test with: 0.17.0-preview.42 (2020.3.41f1, 2021.3.13f1, 2022.1.20f1) (Errors due to dependencies)
Reproducible on: Windows 10
Comments (2)
-
prawn-star
Dec 07, 2023 21:26
Hey STARFLUKE
Sometimes I can stop this by just opening a different scene. Instead of shutting Unity down and restarting it.
-
StarFluke
Jan 19, 2023 15:16
These errors begin filling my console whether Play Mode is on or off. The only option is to close Unity and restart Unity (which can take a long time for some projects.)
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
- GameObjects change Hierarchy order when undoing adding Component to multiple GameObjects
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
Resolution Note:
Fixed in PR 10259