mirror of
https://github.com/brl/mutter.git
synced 2025-02-26 09:44:10 +00:00
9693462f32
Apparently it can happen that a timeline tries to pick a frame clock from an actor that's on a stage, but the actor still doesn't find a frame clock and returns NULL. This probably is the case when starting a timeline right after attaching an actor to a newly created stage, so before the first stage-update cycle. In this case clutter_actor_update_stage_views() will not have run and the stage-actor will have priv->stage_views set to NULL even though there are stage views. To prevent this from happening, use the complete list of stage views maintained by the backend when picking a frame clock for the stage. This doesn't fix any issue appearing on master, but is correct nonetheless. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1631>