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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment