Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.2.1p2
Issue ID
991724
Regression
No
BackgroundWorker's completion callback doesn't get called at the end of the task
To reproduce:
1) Create new project
2) Create and open new C# script
3) Add this function to it (and necessary using's):
[UnityEditor.MenuItem("Window/Test BackgroundWorker")]
private static void TestBackgroundWorker()
{
var w = new BackgroundWorker();
w.RunWorkerCompleted += (o, e) => UnityEngine.Debug.Log("Completed");
w.DoWork += (o, e) => { UnityEngine.Debug.Log("Background task start"); Thread.Sleep(1000); UnityEngine.Debug.Log("Background task end"); };
w.RunWorkerAsync();
}
4) Save the script
5) In top menu bar, select the new menu option you created (Window/Test BackgroundWorker)
Expected: You should get three messages - task start, end and completion
Actual: Completion message doesn't fire
Does not happen in play mode - all three messages fire there
Reproduced in 2017.1.0f3, 2017.2.1p2, 2018.1.0b3
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
- Create Node Menu is not closing and “NullReferenceException: Object reference not set to an instance of an object” error is thrown when Shader Graph window is closed
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
msue2
Dec 19, 2019 10:21
In the Editor, the background worker's completion callback is not called still, in case the Editor enters play mode during background execution. The thread appears to be silently terminated (2019.2.1f1).