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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
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.