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
- Font Asset Creator results bright font colors are not light theme friendly
- Font Asset Creator Font Atlas preview disappears when saved
- When an application is built with Development Build, it results in increase in GUI.Repaint due to DeveloperConsole calls
- Font Asset Creator Font Face dropdown is active but does nothing when clicked if the Font has Include Font Data disabled
- Crash on PPtr<Shader>::operator Shader*() const when Calling Resources.UnloadUnusedAssets() in a specific project
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)
APSchmidt
Dec 04, 2018 17:15
Same for me in 2018.2.xf1. See: https://forum.unity.com/threads/unity-2017-1-p2-issue-with-guiutility-hotcontrol.487528
FireHawkX
Nov 21, 2018 05:26
Just got this error in 2018.11.f1
also with
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
under it
Elringus
Oct 21, 2018 17:34
Still reproducible with Unity 2018.3.0b6
Artifact-Jesse
Sep 08, 2018 07:13
Just saw this in 2018.2.6f1 and Visual Studio Community 2017 (v15.6.5) when closing a custom editor window that was not allowing its position to be dragged.
beard-or-die
Aug 19, 2018 22:13
I get this too in Unity 2018.2.0x-ImprovedPrefabs