Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
12
Found in
2017.2.0f3
2018.3.3f1
2019.1.0a11
2019.2.0a1
Issue ID
1126231
Regression
No
Throwing exception in async method in start spams console, does not stop after leaving the Playmode
To reproduce:
1. Open the attached project
2. Play the SampleScene
Expected: Only a single exception is thrown
Actual: Exceptions start spamming the console, even when not in the Playmode
Reproduced 2018.3.5f1, 2019.1.0b3, 2019.2.0a5
Reproducible with Start(), Awake() and Update()
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
- Graphics Settings RP Asset is changed to None when you press the Escape Key in Object Picker and choose to Continue
- Dedicated Server player crashes on complex HDRP project
- [Mac] Dedicated Server build only decreases Memory usage, CPU time and Build size remain the same as Standalone
- [Linux][Mac] Executing Build And Run with Dedicated Server platform does not open Terminal
- [deprecated] BuildOptions.EnableHeadlessMode needs clearer warning for its conflicts with BuildOptions.subtarget field
ElasticSea
May 04, 2019 18:20
It has been backported to Unity 2018.3.9. https://unity3d.com/unity/whats-new/2018.3.9
t_sun_asobimo
Apr 05, 2019 07:02
Unbelievable, this bug has seriously affected production, and now most of my project's asynchronous code can't work.
Yes, I know. If you don't lose your temper in the forum, then no one will pay attention to you.
simontang_unity
Mar 15, 2019 23:01
I Just encountered/reproduced this and would also love to see this backported, as it seems 2019.2 is a ways out, and we are using async functions on current released builds
ELaino
Mar 11, 2019 10:27
We are using unity 2018.3 with async methods and we really need this to be backported.
M_R
Mar 05, 2019 18:07
will it be backported to 2018.3 / 2018 LTS?