Skip to content

Conversation

@Tyriar
Copy link
Member

@Tyriar Tyriar commented Feb 1, 2017

Fixes #519

@Tyriar Tyriar added this to the 2.3.0 milestone Feb 1, 2017
@Tyriar Tyriar self-assigned this Feb 1, 2017
@Tyriar Tyriar requested a review from parisk February 1, 2017 05:05
Copy link
Contributor

@parisk parisk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Can we pinpoint the issue thought that might call eraseRight with invalid x and y? This way we can fix the root of evil.

@Tyriar
Copy link
Member Author

Tyriar commented Feb 1, 2017

It was running some script that was piping data between xterm.js and a remote server, I think it was happening due to either interleaved CSI codes or the delay between server and host. I'll keep an eye out.

@Tyriar Tyriar merged commit 4de7ed4 into xtermjs:master Feb 1, 2017
@Tyriar Tyriar deleted the 519_erase_null_check branch February 1, 2017 07:51
@Tyriar
Copy link
Member Author

Tyriar commented Feb 1, 2017

Looks like the remote process was running with different dimensions to the xterm.js instance which likely caused this.

@Tyriar Tyriar modified the milestone: 2.3.0 Feb 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants