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
robinsail
Feb 26, 2020 15:56
Getting this in Unity 2019.2.4f with Visual Studio 2017, v 15.7.4
Little_Robot_Guys
Nov 17, 2019 13:45
Still seeing in 2019.2f1 under same steps. This is not fixed.
daisySa
Aug 27, 2019 23:12
Still occurring in 2018.4.5f1.
Rodolfo-Rubens
Jun 08, 2019 21:57
Still present (a lot present) in 2019.3.0a5
rustihkov
Jun 08, 2019 16:56
I found that reloading the solution in VS cleared this up. Double click on the script in Unity, then click reload solution inside VS for each of your scripts.
Symbology
Jun 06, 2019 04:42
Using unity 2019.1.3f1
I was resolving this error (https://support.unity3d.com/hc/en-us/articles/206924676-What-is-CS0108-) when it popped up. I was simply renaming my variables I had done 2 out of the three when it popped up. I have saved my project and am happy to deliver to you guys.
bluekojii
Jun 04, 2019 07:17
2019.1.2f1 getting this weird msg
abegue
May 15, 2019 14:29
Still present in 2019.1.0f2
JamieRoss95
May 06, 2019 22:45
Still present in 2019.1
a-t-hellboy
May 05, 2019 08:58
Fix this issue please. It is in 2019.1.1 too.