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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment