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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment