Search Issue Tracker
Fixed in 2017.3.0f3
Votes
13
Found in
2017.1.0b9
Issue ID
920527
Regression
No
Unity crashes when debugging with VS2017 when using .NET 4.6
Reproduction steps:
1. Open project attached (Quiz1.zip).
2. Open scene "MenuScreen".
3. Open script "onClick" with VS2017.
4. Add breakpoint to Start() function.
5. Attach VS debugger.
6. Press play.
7. Make few steps and exit play mode.
8. Press play again.
Expected result: Player will enter play mode correctly, it will be possible to debug.
Actual result: Unity crashes (bug reporter does not appear).
Note: It works fine when using .NET 3.5. Debugger exits when pressing Play with VS2015
Reproduced on: 2017.1.0b3, 2017.1.0b9, 2017.2.0a4, 2017.3.0a5
-------------------------
Fixed by VSTU 3.4.0.2, not Unity itself.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
rsahel
Feb 28, 2018 12:53
Just updated to Unity 2017.3.1p2 and this issue started to appeared... Updated VS to 15.5.7 to no avail.
cmbellman
Jan 26, 2018 09:18
Just updated to vs2017 15.5.5 and still happening. Unity crashes as soon as a debug breakpoint is hit.
Reticulatas
Aug 27, 2017 00:38
FIXED
Updating to Visual Studio 15.4 preview build resolves this issue.
Reticulatas
Aug 21, 2017 15:04
( Dupe exists here: https://issuetracker.unity3d.com/issues/unity-crashes-when-debugging-using-net-4-dot-6 )