Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
5.6.0f3
Issue ID
913167
Regression
Yes
IEnumerator stops working when adding a Graphic component to a gameObject in a layout group
To reproduce:
1. Open attached Unity project "layoutbug.zip"
2. Open scene "Bug"
3. Go into Play Mode
Expected result: IEnumerator function should not stop working until the end of it.
Actual result: IEnumerator function stops working when it reaches the first yield statement after adding a graphic component to a gameObject in a layout group.
Reproduced in: 5.6.0b8, 5.6.0f1, 5.6.1p1, 2017.1.0b1, 2017.1.0b6
Not reproduced in: 5.5.3p3, 5.6.0b7
Note: adding a graphic component to a gameObject before parenting it to a layout group does not produce the bug (see gameObject "NoBug")
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment