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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.