Search Issue Tracker
Fixed
Votes
0
Found in
2017.2.0b10
Issue ID
949145
Regression
No
Setting a breakpoint for void Start() function and going into play mode while debugging crashes Unity
To reproduce:
1. Open attached Unity project "test_unity3d.7z"
2. Open "scene" scene
3. Open "script.cs" in visual studio
4. Make a breakpoint at void Start() (line 12)
5. Click Attach to Unity to start debugging
6. Go into Play mode
Result: Unity Editor has stopped working... (see attached gif "stoppedworking.gif")
Note: you can write whatever code into the start function, it will always crash, so it is not fun() function inside start that is faulty
Reproduced on: 5.6.4p1, 2017.1.2p2, 2017.2.0f3, 2017.3.0b6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment