
So that if somehow it does return early then we're not left with an allocated `clutter_frame_clock_new_frame` that is never dispatched (which then leads to the pool being exhausted a frame or two later). It's not yet clear how it comes to this where the source is dispatched and the state unscheduled, but at least the more detailed logging here will help us to identify which state it came from. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/3945 Fixes: 394bf5ab24 ("clutter/frame-clock: Add triple buffering support") Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4316>