DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Ko09oDbiwaj1vCky
	5n3G77Ov1iuaZ973sz89LQmGgmz/6DUMDwJyZzZy89o6v5hqGypC4USmTSRliQ4l
	05bFtOUGwcwpUXBLRZW24FzmjbxixSr/IxPyMFD5Ksuw+aJvepomlHh2SPtFeq4A
	wUejScJrGXCJR803EUa3Kgwd/Pw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Reply-To: davek AT 6thstreetradio DOT org
Subject: Re: mintty slow refresh rate over RDP
To: cygwin AT cygwin DOT com
References: <ebe91bf3-6eae-f7b7-7f54-10ad11e2fc20 AT gmail DOT com> <7339de60-cc38-ff7e-224c-0fa239962a11 AT baur-itcs DOT de> <293c3f88-ffb7-3d83-bdfb-46229887050d AT gmail DOT com> <5BFC756C DOT 50007 AT tlinx DOT org> <f26c8f0d-e5ae-0e16-208c-0f2cce4e9ad8 AT towo DOT net> <db0a3d36-f779-f684-c89e-c8ea739a60de AT SystematicSw DOT ab DOT ca> <CAAD4mYi6uNHUWwBVdCn705VXKV4ax=LLXAV1zZqNqPW2ygetfA AT mail DOT gmail DOT com>
From: David Dombrowsky <6thstreetradio AT gmail DOT com>
Message-ID: <aa44389f-c7c1-a974-540d-1c15d29ac024@gmail.com>
Date: Tue, 27 Nov 2018 14:23:26 -0500
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <CAAD4mYi6uNHUWwBVdCn705VXKV4ax=LLXAV1zZqNqPW2ygetfA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 11/27/18 1:14 PM, R0b0t1 wrote:
>> Glass ttys needed special hardware because the early uP chips running at low
>> speeds with small ROMs could not do much between displaying lines.
>> VT100 smooth scroll with No Scroll key toggle was like having more/less built in
>> to the terminal; VT52 had a Scroll key which supported something similar.

NOW you're bringing me back to freshman year :)

I remember building a system from scratch and having no "less" or "more"
tool, and the only way I could find a build error before it scrolled by
was to turn on the "smooth scroll" button.


>>> A good suggestion anyway.
>>> However, if you provide instructions on how to reproduce the issue, I may find
>>> time to check out whether there is some improvement potential.

My use case:
1) run windows 7 in a VM
2) use rdesktop (ubuntu xenial, rdesktop Version 1.8.3) to connect to
the windows box's desktop (used to run visual studio, etc.)
3) launch mintty, maximize the window
4) run a build that spits out a lot of logging.  This can be simulated
with "od /dev/urandom".

On my machine, it will lock up the desktop for a while, until I can
switch desktops, ssh into the windows box, and kill the offending process.

This is certainly multiple bugs, since X11 shouldn't lock up in any
case.  However, I can play fullscreen video over rdesktop without an
issue, so I'm not sure why the console is so graphically intensive.

> More recent RDP sessions should fix this. They do not send GDI calls
> and instead capture the screen at intervals and compress it. 

This is true.  Unfortunately, none of them have made it into distros
yet.  A local build of xfreerdp 2.0 will work fine, BUT that version
removes a few features I use [insert oblig XKCD here].  So *shrug*.


-- 
David Dombrowsky, Software Engineer
davek AT 6thstreetradio DOT org | 518-374-3204
https://www.linkedin.com/in/david-dombrowsky-94334415

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple