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
-
shubhamswaraj2021
Aug 18, 2020 16:51
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
-
Pnvanol
Jun 25, 2019 15:44
still broken in 2019.1
-
KevinDEX
Jan 29, 2019 15:50
KYUNGSUNGCHO - deleting all my watches worked as well
-
KyungSungCho
Jan 06, 2019 08:39
I had the same problem.
So I deleted all the items from the Visual Studio Watch Window Debugger. So my problem was solved.
Perhaps my problem was running GetComponentInChildren() in the watch window. -
radix_greg_presland
Sep 20, 2018 15:36
Continuing to happen in Unity 2018.2.8f1 with Visual Studio extension _Visual Studio 2017 Tools for Unity_ ver 3.8.0.6.
-
cgrow67
Sep 17, 2018 20:40
This isn't resolved at all.
Happens to me in 15.4 all the time. -
rfgsoftware
Sep 09, 2018 10:16
I have the latest version of Visual studio for Mac and Unity 2018.2.6f1 . I have checked and no update are required on Visual Studio. When I try to attach the debugger, Unity crashes.
-
amcakebread
Aug 16, 2018 11:08
still completely broken on Unity 2018.2.1f1 and VS 15.7.5
VS freezes and debugging is more or less completely impossible
I am beginning to think developing using Unity is a big mistake
-
guneyozsan
Jul 28, 2018 23:36
I still have this on 2018.2.0f2 and 2018.2.1.f1 with Visual Studio 15.7.5.
-
olesa79
Jul 05, 2018 14:26
I just had this problem with VS 15.7.4 (with tools for unity 3.7.0.1) and unity 2018.1.6f1.
After doing a little testing, I could only reproduce the problem in one class that implements IDropHandler and another that implements IBeginDragHandler/IDragHandler/IEndDragHandler.
Unity breaks and the breakpoint highlights in VS as expected, but Unity crashes immediately.
In other classes (I only tested 3-4), debugging works just fine.
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