Search Issue Tracker
Fixed in 2018.1.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X
Votes
1
Found in
2017.1.1p2
Issue ID
951901
Regression
No
Editor stops responding when stepping into method and stopping debugging in Visual Studio 2017
Steps to reproduce:
1. Open attached project
2. Open "dds_test" scene
3. Open "dds_script" script with Visual Studio 2017
4. Insert a breakpoint in line #10
5. Attach debugger to Unity
6. Enter play mode
*breakpoint will be hit on Start()*
7. While 'Step Into' option is available, step into
8. Once there aren't any debugging options left, stop debugging
9. Switch to Unity Editor
10. If by now Editor keeps responding, click 'Enter Play Mode' button
Actual result: Editor stops responding
Reproducible with: 5.6.3p3, 2017.1.1p2, 2017.2.0f1, 2017.3.0a7
Fixed in: 5.6.4p2, 2017.2.0p2, 2017.3.0b6, 2018.1.0a2
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Value discrepancy between LateUpdate and OnAnimatorIK when state transition occurs
- Keyword space mismatch error is constantly appearing in the Editor Console window when shaders contain compilation errors
- Inspector Window Tag Search Bar is not populated with the copy-pasted text when using CTRL+V to paste a tag name
- CompilationPipeline.assemblyCompilationFinished is not invoked when using RequestScriptCompilationOptions.CleanBuildCache
- Error “A renderer material mask can't store more than 128 materials.“ is present when the GPU Resident Drawer is disabled
juannieto
Oct 30, 2017 20:10
Fixed and include in https://unity3d.com/unity/qa/patch-releases/2017.1.2p2
- (951901) - Scripting: Fixed crash in debugger when trying to stop while a single step operation is in progress.