From: Benjamin Otte <otte@redhat.com>
Date: Tue, 9 May 2023 12:38:24 +0000 (+0200)
Subject: frameclock: Keep more history
X-Git-Tag: archive/raspbian/4.12.3+ds-1+rpi1~1^2^2^2~22^2~1^2~288^2~1
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=c227493c6577cd5080f86f7bc982ed7d8f190a8b;p=gtk4.git

frameclock: Keep more history

Not all frames get timing info with GDK_DEBUG=no-vsync, so make sure
that even when we render tons of frames, the one frame that does get
timing info is still there when the timing info arrives.

I set it to 128 from 16 now.
This is roughly good enough to go to 5000fps from on a 60Hz monitor.
---

diff --git a/gdk/gdkframeclock.c b/gdk/gdkframeclock.c
index 656849b411..9787be59b9 100644
--- a/gdk/gdkframeclock.c
+++ b/gdk/gdkframeclock.c
@@ -79,7 +79,7 @@ static guint signals[LAST_SIGNAL];
 
 static guint fps_counter;
 
-#define FRAME_HISTORY_MAX_LENGTH 16
+#define FRAME_HISTORY_MAX_LENGTH 128
 
 struct _GdkFrameClockPrivate
 {