Search Issue Tracker
Duplicate
Votes
0
Found in
2018.2.0b2
2018.2.0b4
Issue ID
1036919
Regression
Yes
[Mac]Multiple instances of Visual Studio are opened when selecting to edit a script in the Editor
How to reproduce:
1. In a new Unity project create a Script
2. Attach the Script to any GameObject
3. Open the Script by double-clicking it or clicking the gear icon in the Script Component and selecting "Edit Script"
Expected result: Visual Studio opens only one instance of itself
Actual result: Visual Studio opens up two instances of itself
Reproducible with: 2018.2.0b2, 2018.2.0b8, 2018.3.0a1
Not reproducible with: 2017.4.5f1, 2018.1.5f1, 2018.2.0b1
Notes:
Opening the script from the editor while an instance of Visual Studio is already running opens up a new instance of Visual Studio instead of refreshing the one that is currently running
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
This is a duplicate of issue #1030688