Search Issue Tracker
Fixed in 0.3.0
Votes
0
Found in [Package]
0.2.6-preview
Issue ID
1140853
Regression
No
[UI] Using "detect input to bind to an Action" sometimes generates an error about leaked memory.
GitHub: https://github.com/Unity-Technologies/InputSystem/issues/467
Repro:
1. Download package and project at: https://github.com/Unity-Technologies/InputSystem
2. Right click in the Project window to create a new InputAction or open an existing one
3. In the UI, create new Action Maps and Input Action if there is none
4. Pick a binding, in the Properites, click the ◉ button then press any key to bind it
5. If the error doesn't appear, repeat the last step several times.
Actual: Memory leak error occurs when using UI to bind to an Action through detecting input
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
Add comment