From 15fec034df9b4af1c1aa5f90dbcef3b28d2ca983 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Thu, 16 May 2019 19:45:30 +0000 Subject: [PATCH] always record a frame end time when profiling We need to keep this time, or we may end up with negative frame intervals. --- gdk/gdkframeclockidle.c | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/gdk/gdkframeclockidle.c b/gdk/gdkframeclockidle.c index a917176993..bb1e9c359c 100644 --- a/gdk/gdkframeclockidle.c +++ b/gdk/gdkframeclockidle.c @@ -461,12 +461,11 @@ gdk_frame_clock_paint_idle (void *data) /* the ::after-paint phase doesn't get repeated on freeze/thaw, */ priv->phase = GDK_FRAME_CLOCK_PHASE_NONE; - -#ifdef G_ENABLE_DEBUG - if (GDK_DEBUG_CHECK (FRAMES) || gdk_profiler_is_running ()) - timings->frame_end_time = g_get_monotonic_time (); -#endif /* G_ENABLE_DEBUG */ } +#ifdef G_ENABLE_DEBUG + if (GDK_DEBUG_CHECK (FRAMES) || gdk_profiler_is_running ()) + timings->frame_end_time = g_get_monotonic_time (); +#endif /* G_ENABLE_DEBUG */ G_GNUC_FALLTHROUGH; case GDK_FRAME_CLOCK_PHASE_RESUME_EVENTS: