Hi there I understand that the assemblies do not get reloaded when you stop the game in the editor, hence async methods continue to execute despite the fact that you stopped the game in the editor. An example of a dangerous scenario: - On Awake, an Async method waits 10 seconds, then destroys that gameobject. - The user hits play in the editor. - The user hits stop before the 10 seconds are up - now, in edit mode, the 10 seconds are up and the gameobject destroys itself. - user saves the scene without realizing - losses work... 1) I don't think many people are aware of this. Every time I bring it up on Reddit, people thank me because I just helped them Dodge a bullet. 2) I think the "expected" behavior is for the async methods to stop executing like coroutines when you stop the game in the editor. 3) If nothing is done by Unity to prevent execution after stopping the game in the editor, then the work falls on us developers. We have to make sure we add Application.IsPlaying checks after every await.. just to patch around something that is only an issue in the editor. Not to mention the fact that you have to know about this quirk in the first place.