Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.4
2019.3.0f1
2020.1
Issue ID
1222914
Regression
No
Touch input from a touchscreen monitor is never cleared when debugger gets triggered when input starts
Reproduction steps:
1. Download and open the attached project "1222914.zip"
2. Open the Sample Scene
3. Open LeakTouchInput script in Visual Studio
4. Add a breakpoint to line 12 and attach the debugger to Unity
5. Enter Play mode
6. Press anywhere on the Game window using a touchscreen monitor
7. Press Continue multiple times in Visual Studio
Expected result: Breakpoint is not triggered after the touch input has ended
Actual result: Breakpoint is triggered every frame
Reproducible with: 2017.4.37f1, 2018.4.18f1, 2019.3.4f1, 2020.1.0a25, 2020.2.0a1
Reproduced on: Dell P2418HT
Notes:
The issue does not reproduce all the time but rather consistently (3 out of 5 times).
The touch is only cleared on editor restart.
The user has reported that the issue can be reproduced without debugging, however, this happens inconsistently.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] 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
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment