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
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
Tarrag
Aug 13, 2018 17:32
happening to me too, 2018.2.2f1, error mssg when stopping editor play ->
Should not be capturing when there is a hotcontrol
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
AutoFire-II
Aug 10, 2018 23:45
I just had this happen to me twice in a row on 2018.2. If there's no way to reopen the bug report I'll probably make a new one.
Tarrag
Aug 01, 2018 13:48
happening to me sometimes - say once every 5 builds, can't quite repro , it just comes up randomly, using ARFoundation sample on Unity 2018.2.1f1
WheresMommy
Jul 11, 2018 06:38
Happened to me in 2018.2 too
LEDWORKS
Jun 21, 2018 09:17
Still getting this in 2018.1.5f1 same cause as listed
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....