Search Issue Tracker
Not Reproducible
Votes
3
Found in [Package]
1.7.0
1.8.0-pre.2
Issue ID
ISXB-736
Regression
No
UnityEngine.InputForUI script memory leak when using InputSystem
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/SampleScene“ Scene
3. Open the Memory Profiler window (Window > Analysis > Memory Profiler)
4. Build and Run the project (File > Build and Run)
5. Attach the Memory Profiler to the launched Player
6. In the Memory Profiler, capture a memory snapshot
7. After about 15 minutes, capture another snapshot
8. Select the captured snapshot and select All Of Memory
9. Find the “UnityEngine.InputForUI.Event[]“ script memory usage (Managed > Managed Objects > UnityEngine.InputForUI.Event[])
10. Find the same script memory usage in the memory snapshot from step 6
11. Compare the memory usage values
Expected result: The memory usage of the script did not increase
Actual result: The memory usage of the script increased and continues to increase
Reproducible with: 1.8.0-pre.2 (2023.2.5f1, 2023.3.0b1), 1.7.0 (2023.2.5f, 2023.3.0a14), 1.6.1 (2023.2.0b1)
Couldn't test with: 2021.3.34f1, 2022.3.17f1 (UnityEngine.InputForUI script was only added from 2023.2.X forward)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: The speed, at which the memory usage of the script increases, varies
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
- Unity crashes during the scene template selection in the "Inspector" tab
- [Android] [iOS] [UnityWebRequest] Requests with "UnityWebRequest" are open for SSL Proxying
- SetWindowsHookEx does not prevent Windows key input when Editor or Player Window is focused and Active Input Handling is set to “Input System Package (New)” or “Both”
- Crash on GetEffectiveBc7TextureCompressor() when loading and unloading all Assets in the Project
- Terrain Masks do not ignore the mipmap limit
Resolution Note:
Using latest Unity 6 and Input System 1.12.0 we can no longer reproduce this issue.
If you can still reproduce this using the same updated versions please reopen this case.