search

xibbon / LaTerminal

50 stars 2 forks source link

Crash on fast / lots of scrolling #75

Open michaeljon opened 1 year ago

michaeljon commented 1 year ago

I've been able to repro this on connections into both Ubuntu and MacOS servers. A simple tree command from a home directory causes the terminal connection to close.

This is the log output. If there's another logging level to turn on let me know.

2023-05-01 14:51:48 +0000 [info] La Terminal 1.2.4 #969 2023-05-01 14:51:48 +0000 [nwconnection] Starting connection to 192.168.50.94:22 2023-05-01 14:51:48 +0000 [nwconnection] [SID=10] state .preparing 2023-05-01 14:51:48 +0000 [nwconnection] [SID=10] state .ready 2023-05-01 14:51:48 +0000 [ssh] [SID=10] sending handshake 2023-05-01 14:51:48 +0000 [ssh] [SID=10] userAuthenticationList: publickey,password 2023-05-01 14:51:48 +0000 [ssh] [SID=10] attempting authentication with public key Homenet 2023-05-01 14:51:48 +0000 [ssh] [SID=10] authenticated 2023-05-01 14:51:48 +0000 [preservator] Setting up preservator connected=false reconnecting=false 2023-05-01 14:51:48 +0000 [preservator] Opening SFTP connection 2023-05-01 14:51:49 +0000 [preservator] Testing Unix vs Windows 2023-05-01 14:51:49 +0000 [preservator] Getting architecture 2023-05-01 14:51:49 +0000 [preservator] Checking matching preservator 2023-05-01 14:51:49 +0000 [preservator] Working preservator found 2023-05-01 14:51:49 +0000 [preservator] Launching preservator 2023-05-01 14:51:49 +0000 [preservator] Preservator ports: 46919 and 38147 2023-05-01 14:51:49 +0000 [preservator] remoteReadOffset=0 lastOffsetReceived=0 sendBuffer.pos=0 delta=0 2023-05-01 14:51:49 +0000 [ssh] [SID=9] sending handshake 2023-05-01 14:51:49 +0000 [ssh] [SID=9] userAuthenticationList: publickey,password 2023-05-01 14:51:49 +0000 [ssh] [SID=9] attempting authentication with public key Homenet 2023-05-01 14:51:49 +0000 [ssh] [SID=9] authenticated 2023-05-01 14:51:49 +0000 [ssh] starting up shell 2023-05-01 14:51:49 +0000 [ssh] Shell started up, activating 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 44121 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 93273 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 142425 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 191577 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 240729 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 289881 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 339033 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 388185 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 437337 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 486489 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 535641 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 584793 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 633945 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 683097 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 732249 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 781401 2023-05-01 14:52:03 +0000 [preservator] Notifying remote end that the last seen byte is 830553 2023-05-01 14:52:03 +0000 [info] [SID=9] preservator/data connection closing on channel 26 2023-05-01 14:52:03 +0000 [nwconnection] [SID=10] state .canceled

migueldeicaza commented 1 year ago

Thanks for this bug report, I will take a look.

I have seen this problem in the past with libssh2 and the SSH window negotiation.