https://github.com/ioquatix/script-runner/issues/94
Not sure if this is an issue wiht xterm.js or script-runner. Any ideas?
What version of xterm.js? It's not clear from your package.json if you shipped with 3.3 or 3.4.
I guess it鈥檚 the latest version, because it鈥檚 not pinned to a specific version
I have seen reports of this issue in Atom IDE's terminal as well, which recently upgraded from 3.1.0 to 3.4.1. Possibly it could be some race condition in the access to the buffer object or a missing bounds check? I did not dig into it too much yet.
stack trace points to this line: https://github.com/xtermjs/xterm.js/blob/master/src/Linkifier.ts#L175, I don't have a consistent repro
script-runner is a terminal for Atom.
I'm guessing this happens when the start line of a set of wrapped rows has been trimmed from the top of the buffer and the latter part of the wrapped line is trying to be linkified. Might be wrong though, just adding a null check to prevent it going to -1 should suffice.
@pelmers 馃憢
If it helps, I was able to reproduce this by jumping into a tmux session, cat'ing a large file, scrolling up, and resizing the terminal.
Most helpful comment
If it helps, I was able to reproduce this by jumping into a tmux session, cat'ing a large file, scrolling up, and resizing the terminal.