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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment