Search Issue Tracker
Duplicate
Votes
0
Found in
2018.3.0b2
2018.3.2f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1156634
Regression
Yes
Unity crashes when jumping out of Debugged Async method with Shift+F11
Steps to reproduce:
1. Open users attached project "Async debug crash.zip"
2. Navigate to Project -> Assets -> Scenes and open SampleScene
3. In the Assets folder Open "AsyncDebuCrash" script in Visual Studio
4. Put a BreakPoint at line 19.cs
5. Start Debugging with "Attach to Unity" Debug mode
6. Enter Play mode in Unity
7. When Visual studio reaches a breakpoint press Shift+F11
--Observe the crash
Actual results: Unity Crash
Reproducible with: 2018.3.0b2, 2018.4.2f1, 2019.1.5f1, 2019.2.0b5, 2019.3.0a4
Not Reproducible: 2017.4.28f1, 2018.2.21f1
Note: BreakPoint is not working in versions lower than 2018.3.b2
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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
This is a duplicate of issue #1153078