Search Issue Tracker
Fixed in 5.3.0
Votes
0
Found in
5.3.0b2
Issue ID
735607
Regression
Yes
5.3.0b2 crashes on Windows when debugging on Visual Studio 2012/2013/2015 and UnityVS
Steps to reproduce:
1. Open attached project
2. Open 'NewBehaviorScript' with Visual Studio
3. Attach Visual Studio to Unity debugger
4. Press Play in Unity
5. Editor will crash
Comments (5)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
StormMuller
Nov 24, 2018 00:47
Issue not fixed. just happened to me on 2018.2.15f1
DDeathlonger
Jul 28, 2018 13:40
Just happened to me on 2018.2.1f1
diegoleao
Jul 28, 2018 01:00
Unity 2018.1.1f1 and VS 2017, same problem. Sent here by the error popup too. Unity was compiling in the background, when I focused on it, it crashed.
Finlay_McGrath
Jul 17, 2018 11:39
I've just had this happen in Unity 2018.2.0f2 and Visual Studio 2017 then was sent here by the error popup.
Chiodini
Feb 09, 2016 12:48
I have a similar problem with VS 2015, VSTFU 2.1.0.0 in Unity 5.3.1f
Any workaround?