Search Issue Tracker
By Design
Votes
0
Found in
2021.2.0a18
2021.2.0b12
2022.1
Issue ID
1367206
Regression
Yes
Unhandeled exceptions are thrown when debugging with JetBrains Rider IDE
Steps to reproduce:
1. Open the attached "case_1367206_repro" project
2. Select any version of Rider IDE in Edit > Preferences > External Tools > External Script Editor
3. In Project windows open Assets > "UnhandledExceptionClass.cs"
4. Select "Attach to Unity Editor & Play" in Rider IDE
5. Select Run > Debug from the main menu in Rider IDE
Expected result: no unhandled exceptions are thrown in Rider IDE
Actual result: unhandled exception is thrown in Rider IDE
Reproducible with: 2021.2.0a18, 2021.2.0b14, 2022.1.0a11
Not reproducible with: 2019.4.34f1, 2020.3.20f1, 2021.1.24f1, 2021.2.0a17
Note:
- workaround for this issue in Rider IDE is to uncheck "Brake on unhandled exceptions"
- in 2021.2.0a18 Mono was updated from 5.11.0 to 6.13.0
- no unhandled exceptions are thrown in Microsoft Visual Studio
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (2022.1.X):
Reverted behavior in 2021.2 to not break on unhandled exceptions. However this behavior is actually intended and is due to a bugfix from upstream mono (https://github.com/mono/mono/pull/15234). We have decided to push back the introduction of this behavior to allow for a smoother reintroduction of it later.