Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
5
Found in
2017.1.0f3
Issue ID
930062
Regression
No
Unity crashes when debugging using .NET 4.6
Steps to reproduce:
1. Download FarmManagementGame.zip project and open
2. Set up a breakpoint in GrowingState.cs at line 30
3. Attach to Unity and press play
4. Press one of the white squares wait a bit and repeat this step two more times
5. When breakpoint triggers step into it
Results: editor crashes when stepping into line 31. Doesn't reproduce when using .NET 3.5
Note: .NET 4.6 was introduced in 2017.1, 2017.2
Reproduced with: 2017.3.0a7 2017.2.0b2, 2017.1.0f3
-
mbrindic
Jun 28, 2018 08:06
I'm using Unity 2018.1.3 and the issue is still there... I tried deleted all visual studio files, and nothing changed...
-
Thomas-Mountainborn
Jun 26, 2018 13:50
This is NOT fixed!
-
Airat1995
Jun 18, 2018 14:38
I have the same problem but in my project. Please reopen issue tracking.
-
A_Tlos
Jun 12, 2018 08:12
Reproduced with Unity 2018.1 and Visual Studio 15.7.3
-
GoGoBlitz
Jun 11, 2018 16:24
Still reproduced in 2018.1
-
stevendevries
Jun 01, 2018 02:20
I had the same problem (Unity 2018.1 - VS2017 - 15.5.1), Re-importing all assets did not help for me.
I had switched the Scripting Running version from '.NET 3.5x equivalent' to .'NET 4.x equivalent' because i thought the newer the better. That's when the crashing of unity began. When i switched it back my problem was fixed.
File\Build Settings\Player Settings\Other Settings\Scripting Running version\.NET 3.5x equivalent
I hope it will help you to.
-
LurchUSA
Apr 10, 2018 16:51
Fixed in unity 2017.3? You're kidding right?
I get unity editor crashes intermediately, when Visual Studio is stopped at a breakpoints and I hover my mouse cursor over a variable at the break point.
I have re-sharper installed and have turned off all re-sharper debugging integration, which I was told by Unity support to do, but the crash still happens.
When it DOES happen, I have to delete ALL Visual Studio files within the unity project folder and the "assetDatabase3" file, within the project library file, before I can get Visual Studio working again. If I do not do this, as soon as I land on ANY break-point... Unity crashes!
-
russ_unity3
Feb 12, 2018 17:20
It works a little bit better for me. I can connect the debugger, run unity, and it will hit most of my breakpoints. If I leave the debugger connected, I can work for quite a while before it crashes. If I stop the debugger, Unity will freeze every time.
I have seen this behavior consistently across a few different projects. Is this a Unity problem, or a VSCode problem?
Visual Studio was working perfectly with the debugger.... until it decided it didn't want to start at all on my Mac.
-
cmbellman
Jan 26, 2018 12:26
Unity 2017.3.0f3 with .NET 4.6 and vs2017 15.5.5 = crash when debug breakpoint is hit
-
Andrram
Nov 08, 2017 20:45
Unity still crashes with VS - version 15.4.3. I can step through a few lines of code, then unity and vs stop working.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2017.3.0f3):
Fix tested with:
Visual Studio tools for Unity - 3.9.0.3
Visual Studio 2017 Version 15.9.4