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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment