Mikael - 2015-10-05

This may because of how TightVNC flushes protocol data?

Also see bug https://sourceforge.net/p/vnc-tight/bugs/1365/ .