Escape Sequences generated During Window Resize

Brought to you by: kzmi, okajima

#45 Escape Sequences generated During Window Resize

Status: open-fixed

Owner: Iwasa Kazmi

Labels: None

Priority: 5

Updated: 2012-02-25

Created: 2012-02-21

Creator: jonburnaby

Private: No

Resizing the Poderosa window -- to increase the width -- during the htop command generated two error messages about unknown Escape Sequences. Clicking OK on the first error message dialogue box displayed the second error message dialogue box, as can be seen in the error.log file by the different time stamps on the errors.

Similar to item # 3486809

Discussion

jonburnaby - 2012-02-21

error.log (zipped)

error.log.zip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

jonburnaby - 2012-02-21

summary: Escape Sequences During Window Resize --> Escape Sequences generated During Window Resize
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iwasa Kazmi - 2012-02-21

assigned_to: nobody --> kzmi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iwasa Kazmi - 2012-02-25

The exception is caused by calling SSH2Channel object from multiple threads.
Most of outbound data, like key input, mouse tracking, or response to the request escape sequence,
are transmitted exclusively, but resizing event is not.

"Unknown escape sequence" may be happened by frequent resizing event.
With slow connection, remote application seems to start to refresh screen before the previous screen data is transmitted completely.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iwasa Kazmi - 2012-02-25

status: open --> open-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iwasa Kazmi - 2012-02-25

Exception issue was fixed.
Transmitting methods of SSH2Connection and SSH2Channel are now thread-safe.

Also I added code to ignore apparent incomplete escape sequence.
It reduces "unknown escape sequence" error, but some escape sequence error may still happen.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.