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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
farrukhnawaz
Jul 05, 2020 11:12
https://mobiledady.com/mobiles/
https://rewriter-tool.com/
https://spinbot.rewriter-tool.com/
https://paraphrasing.rewriter-tool.com/
https://seotoolcheckers.com/backlink-maker
https://seotoolcheckers.com/page-speed-checker
sama-van
Jun 14, 2020 03:19
Still going in 2020.2.0a13.
oznogon
May 26, 2020 04:53
Still going strong in the year 2020, 2018.4.23f1
robinsail
Feb 26, 2020 15:56
Getting this in Unity 2019.2.4f with Visual Studio 2017, v 15.7.4
toolparaphrase
Jan 12, 2020 18:35
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.
https://rewriter-tool.com/
https://freearticlespinbot.com/
https://seotoolcheckers.com/backlink-maker
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.
farrukhnawaz
Jun 11, 2019 11:25
Good work. 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.
https://paraphrasingstool.com/
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.