Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.1.X, 2018.2.X
Votes
0
Found in
2018.1.0b13
Issue ID
1027351
Regression
No
System.Diagnostics.Debugger.Break() does not trigger a breakpoint
Steps to reproduce:
1. Download attached project
2. Open "test" scene
3. Enter play mode
Expected results: Breakpoint is triggered by System.Diagnostics.Debugger.Break()
Actual results: Breakpoint isn't triggered by System.Diagnostics.Debugger.Break()
Reproduced with: 2018.2.0b1, 2018.1.0f1, 2017.4.1f1, 2017.2.2p3, 2017.1.3p3, 5.6.6f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment