Search Issue Tracker
Fixed
Votes
0
Found in
5.4.2f2
Issue ID
852360
Regression
No
CustomYieldInstruction coroutine continues to run after StopCoroutine is called
To reproduce:
1. Open attached project "StopCoroutineBug.zip"
2. Go to the Console window.
3. Play "main" scene.
4. Look at the Console window.
Expected result: "WaitForCount" is stopped with StopCoroutine on frame 50.
Actual result: "WaitForCount"is not stopped with StopCoroutine, only stopped with "StopAllCoroutines", on frame 100.
CustomYieldInstruction requires Unity 5.3 or later.
Reproducible with: 5.3.0f1, 5.4.1f1. 5.5.0f2
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
a3dline
Mar 14, 2017 14:45
ios Il2 was crashed for StopCourutine if Courutine is IEnumerator field
greg-harding
Feb 20, 2017 03:55
It's listed as fixed in 5.5.1p4 and 5.6.0b9 (it was my bug report).
roberto_sc
Feb 13, 2017 19:35
Which version fixes this bug???