Search Issue Tracker
By Design
Votes
0
Found in
2020.2.0b4
2020.3
2021.1
2021.1.3f1
2021.2
Issue ID
1329849
Regression
Yes
Visual Studio shows multiple instances of Unity
Steps to reproduce:
1. Download and open the user's project "MultipleDebuggers.zip"
2. Make sure only one instance of Unity Editor is running
3. Open Assets/Log.cs in Visual Studio
4. Go to Debug > Attach Unity Debugger
Expected result: Only one instance of Unity Editor is shown in the Select Unity Instance dialog box
Actual result: There are two instances of Unity Editors shown in the Select Unity Instance dialog box
Reproducible with: 2020.2.0b4, 2020.3.7f1, 2021.1.6f1, 2021.2.0a16
Not reproducible with: 2018.4.34f1, 2019.4.26f1, 2020.2.0b3
Notes:
1. Reproducible on both Windows and macOS
2. Not reproducible in Rider
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Resolution Note:
There are 2 instances in this case because we have 2 Unity processes running. In this case it's the Asset Database process (even says (background) next to it). If you also had e.g. the Out of Process Profiler, it would also show up.