Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
5.6.1f1
Issue ID
925603
Regression
No
Unity crashes after setting a break point at GetComponent<Rigidbody>().angularVelocity in Start when debugging with VS
Steps to reproduce:
1. Open the attached project(WinPhoEdited.zip)
2. Open the Assets/test.unity scene
3. Open the Assets/Spinner.cs script in Visual studio
4. Set a break point on line 11
5. Attach Visual Studio debugger
6. Play the scene
7. Make few steps and exit play mode
8. Play the scene
9. Observe the crash
Expected result: Player will enter play mode correctly, it will be possible to debug
Actual result: Unity crashes
Note:
The crash is not 100% reproducible but it reproduces very often
Reproduced with: 5.4.5p4, 5.5.4p1, 5.6.2p1, 2017.1.0f2, 2017.2.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment