(Case 1143604) The asynchronous function callback method is passed from the Play mode to the Editor

https://fogbugz.unity3d.com/default.asp?1143604_v8qe8bvth3mn1iog.

1. What happened

The asynchronous function callback method is passed from the Play mode to the Editor mode.
Expected behavior: Forced to stop all asynchronous functions when switching Editor/Play mode.

2. How we can reproduce it using the example you attached

Play SampleScene, Stop Play mode. Wait for 10s and will create a cube in the current scene in editor mode. It's wrong.

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4. using System.Threading.Tasks;
5.  
6. public class AsyncBug : MonoBehaviour
7. {
8.     // Start is called before the first frame update
9.     async void Start()
10.     {
11.         Debug.Log(1);
12.         await Task.Delay(10000);
13.         Debug.Log(2);
14.         GameObject go = GameObject.CreatePrimitive(PrimitiveType.Cube);
15.         Debug.Log(3);
16.     }
17. }
18.  

 

Errors can be reproduced in all versions.

 

I receive https://issuetracker.unity3d.com/is...o-run-in-the-edit-mode-when-exiting-play-mode。

 

Yep, this makes async methods very dangerous and ruins the 'sandbox' nature of the editor/play mode.

I've posted about this in a previous beta, here:
https://forum.unity.com/threads/asy...e-in-the-editor-potentially-dangerous.591235/

@mkderoy replied:

Though there is bug reports from as far back as the start of 2018 , and there isn't any more movement on this issue, so I guess don't hold your breath for a solution from Unity any time soon.