Search Issue Tracker
Fixed in 1.1.0-preview.3
Votes
19
Found in [Package]
2019.3.0b6
Issue ID
1190150
Regression
Yes
[New Input System] Enabling Enhanced Touch yields errors related to memory leak
To repro this:
1. Open the attached project ("BugReporter-TouchTimeline.zip")
2. Open the SampleScene
3. Make sure "Touch Simulation" script component on 'Global' GameObject is enabled
4. Enter Play Mode
5. Click and hold the left-mouse button on the Game View window and drag it outside of it
6. Notice "Pointer should have exited all objects before being removed" error in the console
7. Exit and enter the Play Mode again
Expected result: No errors are thrown
Actual result: 'A Native Collection has not been disposed, resulting in a memory leak. Enable Full StackTraces to get more details.' error is thrown
Reproducible with: 2019.3.10f1, 2020.1.0b5, 2020.2.0a7
Couldn't test with: 2017.4, 2018.4 (minimal required package version is not supported)
Reproducible with package versions: 0.9.0-preview, 1.0.0-preview.6
Note: Error is also sometimes thrown after entering the Play Mode when Enchanted Touch API is used (usually after 'Pointer should have exited all objects before being removed' error is thrown in Play Mode)
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
- Timeline section stops rendering after restoring Profiler Window modules
- Cursor image does not update when Cursor.SetCursor is called again with CursorMode.Auto
- Crash on do_runtime_invoke when reopening a specific project after failing to build it
- Animations change speed when rigidbody is added
- Low FPS persists when re-entering Play mode after an extended session in a specific project
Resolution Note (fix version 1.1.0-preview.3):
Fixed in 1.1.0-preview.3 available for 2019.4 and above