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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
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
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