Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.2.0p1
2017.2.0a4
Issue ID
1006074
Regression
Yes
"Should not be capturing when there is a hotcontrol" message thrown after double clicking on runtime error and exiting playmode
How to reproduce:
1. Open the attached "Test" project and "Repro" scene, enter playmode
2. Press "DivideBy0" button and notice the "Division by zero" runtime error
3. Click on error twice to open the script and go back to Unity
4. Exit the playmode with Visual Studio still opened and observe the console
Expected result: No warnings/messages are thrown after exiting playmode
Actual result: "Should not be capturing when there is a hotcontrol" message is thrown
Regression introduced with - 2017.2.0a4
Reproducible with - 2018.1.0b10, 2017.3.1p3, 2017.2.2f2, 2017.2.0a4
Not reproducible with - 2018.2.0a4, 2017.2.0a3
Note: Could not reproduce with Visual Studio Code, reproduced with Visual Studio 2017/Visual Studio 2015
Comments (52)
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
dval
Apr 22, 2018 14:38
NM, I see it should still be present until I upgrade to 2018
dval
Apr 22, 2018 14:37
I get this error in Unity 2017.3.1f1.
So, probably not fixed yet....