Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.7.0
Issue ID
ISXB-624
Regression
No
InputSystem.TryFindMatchingControlLayout is called unnecessarily when undoing the deletion of GameObjects in the Hierarchy
Reproduction steps:
1. Open the attached “repro_IN-47328.zip” Project
2. Open the SampleScene
3. Open the Profiler tab
4. Install the Profile Analyzer package and open its tab (Window → Analysis → Profile Analyzer)
5. Enter the Play Mode
6. Press on the Record button in the Profiler tab
7. Delete all of the GameObjects in the Hierarchy (CTRL+A) and Undo (CTRL+Z)
8. Quickly press the Record button again to stop profiling
9. Go to Profile Analyzer and press Pull Data
10. Observe the “Median” value of the “Menu.Undo” call
Expected result: “Menu.Undo” call lasts for ~30ms or less
Actual result: “Menu.Undo” call lasts for ~100ms or more
Reproducible with: 2021.3.30f1, 2022.3.9f1
Couldn’t test with: 2023.1.12f1, 2023.2.0b8, 2023.3.0a4 (Errors due to deprecated code being used)
Reproduced on: macOS Ventura 13.5 (Intel), Windows 10
Not reproduced on: No other environment tested
Notes:
- This performance degradation could be caused by the InputSystem.TryFindMatchingControlLayout call
- Issue might be not reproducible on some systems, couldn’t find under what conditions this occurs
- Not reproducible on a new project
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
- Crash on "The GUID inside 'Assets/asset.png.meta' cannot be extracted by the YAML Parser." when opening the project
- Shadows disappear when looking at a certain angle in Scene view and using Cloud Shadows with Volumetric Clouds
- Tree leafs are not shown in Scene/Game view when using newly created Tree as a Brush on Terrain
- StackOverflowException freezes or silently crashes the Editor
- Microsoft Surface Device freezes when detaching and reattaching physical keyboard attachment to a Microsoft Surface device in Standalone Player for Windows
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.