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
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
- [Android] [Vulkan] Cubes stuck on the first few frames of rotation and application flickering when an Overlay Camera is added to the Camera Stack with MSAA enabled
- Profiling information icon does not update for Light Mode
- [Linux] Type to select functionality is missing for drop down menus
- TextMeshPro calculates Width Compression incorrectly when using certain values in the WD% field
- VFX Graph link contrasts fail WCAG guidelines
Wunder-Waffe
Mar 26, 2019 09:24
It just happened to me too in 2018.3.10f1 and using Visual Studio 2017. I had Unity and VS opened and at the same time I installed new graphic drivers in the background. I was working on a script and tthen realized that instaling the drivers managed to crash Unity. So I saved the script in VS and then closed both Unity and VS. After reopening I was unable to use the script and got the message and I soon realized that VS changed the public class name to something different. I am sure it's due to Unity being unable to compile while it crashed. I just changed the name back to what the script name was and it works.
loki-of-mute
Mar 23, 2019 14:45
I see it occur still in Unity 2018.3.8f1, although the ticket claims 'fixed'.
Hard to trigger on purpose, but when I look in the console, it's nearly always there (in a large project, don't have it otherwise).
AaronBacon
Feb 23, 2019 01:02
It doesn't seem to affect anything, but Yeh, it's still appearing in 2018.3.6f1
Rezano
Feb 10, 2019 16:46
2018.2.6f1
me too
Marks98
Feb 05, 2019 09:42
I don't think it is solved. I have 2018.3.3f and message still appears.
GabrielSimoes
Jan 25, 2019 22:52
I got this in 2018.3 too
KingKubes
Jan 25, 2019 18:25
Unity 2018.3.2f1
Should not be capturing when there is a hotcontrol
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
SpiccyMayonnaise
Jan 04, 2019 04:03
I got this in 2018.3
Rugbug_Redfern
Jan 03, 2019 03:47
Happened to me with 2018.2.17f1
Shadownildo
Dec 09, 2018 16:29
I'm in 2017.4.11f1 and i'm getting this error, But i don't use any button just Touch/Swipe commands
Should not be capturing when there is a hotcontrol
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)