Search Issue Tracker
Fixed
Fixed in 1.11.1
Votes
0
Found in [Package]
1.10.0
1.11.0
Issue ID
ISXB-1070
Regression
No
Memory leak in OnScreenStick
Description
OnScreenStick is leaking memory when destroyed
Initial setup
Unity with Input System.
Reproduction steps
Add OnScreenStick component, configure it to use isolated actions. Destroy it.
Expected behaviour
OnScreenStick destroys objects it has created.
Actual behavior
Objects created are leaked.
Logs and Links
Fix contributed and reported in PR: [https://github.com/Unity-Technologies/InputSystem/pull/1960/files]
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
Add comment