Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2021.3.29f1
2022.3.7f1
2023.1.8f1
2023.2.0b4
2023.3.0a3
Issue ID
UUM-45667
Regression
No
Exceptions are not thrown when used in a pool of threads
How to reproduce:
1. Open the “IN-49334_ExceptionsIssue“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Observe the Console
Expected result: Exceptions are thrown
Actual result: Exceptions are not thrown
Reproducible with: 2021.3.29f1, 2022.3.7f1, 2023.1.8f1, 2023.2.0b4
Reproducible on: Windows 10
Note: Reproducible in Mono Player, however, not in IL2CPP
Comments (1)
-
ProtoTerminator
Dec 11, 2023 00:58
So it's impossible to capture unhandled exceptions from library code that doesn't handle it themselves.
Swallowing exceptions is such a bad practice. `AppDomain.UnhandledException` exists for a reason, and it's just not working at all in Editor and Mono builds...
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:
For the time being, exceptions generated in threads that were created by a user must be handled by the user. To make sure an exception is caught the threaded code can be wrapped in a try-catch, and the Exception can be logged with Debug.LogError.
Resolution Note (2023.3.X):
For the time being, exceptions generated in threads that were created by a user must be handled by the user. To make sure an exception is caught the threaded code can be wrapped in a try-catch, and the Exception can be logged with Debug.LogError.