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
- “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
Add comment