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

Scripting

-

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)

  1. 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.

  2. bluekojii

    Jun 04, 2019 07:17

    2019.1.2f1 getting this weird msg

  3. abegue

    May 15, 2019 14:29

    Still present in 2019.1.0f2

  4. JamieRoss95

    May 06, 2019 22:45

    Still present in 2019.1

  5. a-t-hellboy

    May 05, 2019 08:58

    Fix this issue please. It is in 2019.1.1 too.

  6. Kogara

    Apr 26, 2019 20:49

    Still having this error in 2018.3.2f1, just running some simple UI scripts.

  7. AzureAngel

    Apr 25, 2019 23:19

    Happening every now and then when developing a simple world scale UI interaction scene

    version 2019.1.0f2 Personal - [PREVIEW PACKAGES IN USE]

    Should not be capturing when there is a hotcontrol
    UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

  8. denlee0710

    Apr 20, 2019 09:06

    Still happening on 2019.1.0f2

  9. merpheus

    Apr 14, 2019 09:33

    This issue still exists in 2018.3.9f1

  10. Wunder-Waffe

    Mar 26, 2019 09:28

    Anyway I am sure this happens when VS and Unity somehow manage to get out of sync when compiling scripts.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.