Search Issue Tracker
Fixed
Fixed in 1.9.0
Votes
3
Found in [Package]
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
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.
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.