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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
This is a duplicate of issue #1033280