-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Be more defensive to prevent issues when resize and writes overlap #661
Comments
Use of the |
I updated to xterm 2.9.1 today and now get this error when opening new terminals. I created the terminal and then attach a resize handler to resize the terminal using the 'fit' addon. I noticed this error happens whenever the initial number of rows when the terminal starts is later increased by the resize handler. I worked around this by setting something like 200 rows when creating the terminal. The specific line that triggered this error for me is at https://github.com/sourcelair/xterm.js/blob/5bc0ad879b7b9cdc3c8617478512ba80affc5d79/src/Renderer.ts#L170 |
Same error here. But if at the start of the ssh session I type |
I was also seeing this problem. The height parameter of the class was set to a relative value, like 40%. When I added a min-height with a specific pixel value, the error went away.
|
Hello again. By the way, I'm that ghost above. Just decided to merge my account to the one I'm using now. Anyway, I've been researching this issue and trying to fix it in my Atom plugin. I've pinpointed it down to a problem involving the less program, at least with my plugin. More on that is here (https://github.com/amejia1/atom-xterm/issues/4). So far, I've just been working around the problem but I think the problem I'm facing could be due to either node-pty or xterm.js. |
@amejia1 have you tried reproducing it on the v3 branch? |
I had since made changes to the atom-xterm plugin. This issue now only appears whenever I use the 'less' program when I resize the terminal from larger to smaller. I reported this at #977 . I'll try the v3 branch. |
I'm closing this off to keep out issue count lower as it hasn't gained any traction, is stale or is not worth tracking. |
#164 (comment)
The text was updated successfully, but these errors were encountered: