Search Issue Tracker
Duplicate
Duplicate in 2021.2.X
Votes
0
Found in
2021.2.0b1
2021.2.0b6
2022.1
Issue ID
1355156
Regression
Yes
Crash on stopping debugging
How to reproduce:
1. Open attached Unity project
2. Open attached script
3. Add some breakpoints and start debugging (left mouse button triggers break point)
4. Stop debugging
5. Observe crash
Expected result: Debugging is stopped, Editor shouldn't crash
Actual result: Editor crashes
Reproduced with: 2022.1.0a4, 2021.2.0b6, 2021.2.0b3.
Didn't reproduce with: 2020.15f2, 2019.4.29f1, 2021.2.0b1, 2021.2.0a1.
Notes:
When debugging build, it still crashes editor, build works as expected.
Not reproducible on Windows.
On macOS, it's reproducible on both Visual Studio and Visual Studio Code.
Comments (1)
-
castor76
Nov 12, 2021 00:21
Still happening with 2021.2.1f1. Making it really difficult to work with.
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
- Only one [UnityOneTimeSetUp] method runs when there are 2 of them in different classes
- Crash with multiple stack traces when Sprites with a high resolution get Sliced to a Grid with a small cell size in the Sprite Editor
- The UI Builder's Data Source Object picker cannot be navigated after triggering a circular dependency dialog box
- Typo on "Chromatic Abberation" and "chromaticAbberationIntensity" when instead it should be aberration
- UI Document (UXML) UI disappears from the Game view when any asset is imported and does not reappear until clicking in the Editor
This is a duplicate of issue #1354671