When we are asked to unthrottle an SSH connection (by the front end
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Sat, 12 May 2012 17:00:54 +0000 (17:00 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Sat, 12 May 2012 17:00:54 +0000 (17:00 +0000)
calling back->unthrottle), we should immediately call
ssh_process_queued_incoming_data to handle the SSH packets that have
been saved for later functioning while we were throttled. Otherwise,
they'll sit there unhandled until the next call to ssh_gotdata, which
might not be for ages if the server thinks it's waiting for us.

git-svn-id: svn://svn.tartarus.org/sgt/putty@9523 cda61777-01e9-0310-a592-d414129be87e

ssh.c

diff --git a/ssh.c b/ssh.c
index 505b4ae..750017f 100644 (file)
--- a/ssh.c
+++ b/ssh.c
@@ -10037,6 +10037,12 @@ static void ssh_unthrottle(void *handle, int bufsize)
            }
        }
     }
+
+    /*
+     * Now process any SSH connection data that was stashed in our
+     * queue while we were frozen.
+     */
+    ssh_process_queued_incoming_data(ssh);
 }
 
 void ssh_send_port_open(void *channel, char *hostname, int port, char *org)