Search Issue Tracker
Duplicate
Fixed in 2017.4.X
Votes
2
Found in
2018.2.0b2
Issue ID
1030828
Regression
No
Coroutines Started within another Coroutine show up under the calling Coroutine's Profiler Sample
How to reproduce:
1. Open attached Unity project "Test Bed copy"
2. Load scene "Scene1"
3. Open Profiler window
4. Enter the play mode
5. Press space to load second scene
6. Wait few seconds and pause play mode
7. Look at the profiler output
8. Expand Update.ScriptRunDelayedDynamicFrameRotate --> CoroutineDelayedCalls --> LoadNextLevel.LoadNextLevelDelayed() [Coroutine: MoveNext]
Expected result: There is no hint, that coroutine from the first scene is still running.
Actual result: The two coroutines appear as though they are a executing as part of the original coroutine.
Reproduced with: 2018.2.0b3, 2018.2.0a9
Note: can't reproduce on 2017, 2018.1 and 2018.2.0a1 - 2018.2.0a8 because of errors.
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
- GPU usage doubles when a project is running in the background
- Memory usage increases significantly when using Global Search
- [URP] Post-effects using UnsafePass in RenderGraph will stop working when "Anti Aliasing (MSAA)" is enabled
- UI Builders incorrectly informs about a circular dependency when the reference in the second UI Document is removed
- TextMeshPro Text is misaligned when it should align in the "flush" style
This is a duplicate of issue #1033280