Search Issue Tracker
By Design
Votes
0
Found in
5.4.1f1
Issue ID
845328
Regression
No
Unity exceptions in asynchronous methods called from UdpClient are not handled
Reproduction steps:
1. Open the "Server.zip" project in VS and start the server
2. Open the "bug.zip" project
3. Open the only scene
4. Play the scene
-Notice in the console that there are no errors, however, the script stops running.
5. Uncomment Try-Catch block and play the scene again
-Notice the Unity exception from the try-catch block in the console.
The message produced by the exception: UnityEngine.UnityException: EnsureRunningOnMainThread can only be called from the main thread
Actual result: No errors are thrown in the console.
Expected result: Exception is handles and error is thrown in the console
Note: In 5.3 the asynchronous methods produce no exceptions and keep running after exiting play mode
Reproduced on: 5.6.0a1, 5.5.0b10, 5.4.2p3.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Add comment