Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
1
Found in
2018.3.3f1
2018.3.5f1
2019.1.0a11
2019.2.0a1
Issue ID
1130295
Regression
Yes
Exception thrown in one async tasks stops all other async methods
Steps to reproduce:
1. Download 1130295_repro.zip and open "SampleScene"
2. Enter play mode
Expected results: Expectation is thrown one time and another async task loop isn't stopped.
Actual results: Exception is thrown multiple times and another async task loop is stopped.
Reproduced with: 2019.2.0a6, 2019.1.0b5, 2018.3.7f1
Not reproducible with: 2018.3.2f1, 2017.4.12f1
Regression introduced in: 2019.1.0a11, 2018.3.3f1
Exception: Exception of type 'System.Exception' was thrown.
NewBehaviourScript+<WaitAndThrowAsync>d__1.MoveNext () (at Assets/NewBehaviourScript.cs:22)
--- End of stack trace from previous location where exception was thrown ---
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () (at <3a07e6401b5d4cc98f7be596cb2130ba>:0)
System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_0 (System.Object state) (at <3a07e6401b5d4cc98f7be596cb2130ba>:0)
UnityEngine.UnitySynchronizationContext+WorkRequest.Invoke () (at C:/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:112)
UnityEngine.UnitySynchronizationContext.Exec () (at C:/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:73)
UnityEngine.UnitySynchronizationContext.ExecuteTasks () (at C:/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:94)
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
- "Problem detected while importing the Prefab file" errors on Learning Templates import
- Crash on RaiseException during Socket.BeginConnect in Player when application connection is blocked through commercial firewall
- Decal Projector produces artifacts when the normal and decal are projected in negative z-direction and Normal Blend is set to 1
- Undoing slider field change only resets slider position, doesn't undo the value change
- Precision changes when a tangent is added to a Vertex node
Resolution Note (fix version 2018.3):
Fixed in 2019.2.0a8
Backported to 2018.3.9f1, 2019.1.0b7