From 3b35daacf734dc824b6101e54d62067fde6016b8 Mon Sep 17 00:00:00 2001 From: nicm Date: Tue, 9 May 2017 13:04:36 +0000 Subject: If the current screen was complex enough, it was possible to make redraw itself hit the "terminal can't keep up" check. To avoid this, record how much data we send during redraw (we know we will be starting with 0) and skip the check until it has been flushed. GitHub issue 912. --- server-client.c | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'server-client.c') diff --git a/server-client.c b/server-client.c index 72b5d312..ae8e0d6e 100644 --- a/server-client.c +++ b/server-client.c @@ -1314,6 +1314,16 @@ server_client_check_redraw(struct client *c) c->flags &= ~(CLIENT_REDRAW|CLIENT_BORDERS|CLIENT_STATUS| CLIENT_STATUSFORCE); + + if (needed) { + /* + * We would have deferred the redraw unless the output buffer + * was empty, so we can record how many bytes the redraw + * generated. + */ + c->redraw = EVBUFFER_LENGTH(tty->out); + log_debug("%s: redraw added %zu bytes", c->name, c->redraw); + } } /* Set client title. */ -- cgit