Search Issue Tracker
Fixed in 2021.3.35f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a3
Votes
0
Found in
2021.3.13f1
2022.1.22f1
2022.2.0b14
2023.1.0a17
2023.2.0a1
2023.3.0a1
Issue ID
UUM-19657
Regression
Yes
[Undo] Error “Failed to create Object Undo, because the action is too large” is thrown when deleting a large GameObject
Steps to reproduce:
1. Open the user’s attached “GameobjectsPoolBug“ project
2. Create a “Pool” GameObject (Bug → CreatePool)
3. Select it in the Hierarchy and delete
4. Observe the Console
Expected result: The pool is deleted without an error
Actual result: Error “Failed to create Object Undo, because the action is too large” is thrown
Reproducible with: 2021.1.0a1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b14, 2023.1.0a17
Not reproducible with: 2020.2.0a21, 2020.3.40f1
Reproduced on: macOS Monterey 12.5.1 (Intel)
Note: Not reproducible when deleting the pool via Bug → DeletePool
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
Add comment