Renderer crash when resizing terminal with text-wrap

Details

• Browser and browser version: Chrome 71.0.3578.98, Safari 12.0.2 (14606.3.4), Firefox 65.0
• OS version: Windows 10 & macOS Mojave
• xterm.js version: v3.11.0

Steps to reproduce

1. Visit: https://4jnl8qxxn4.codesandbox.io/
2. Open browser dev console
3. Click “Play Example” button
4. Observe TextRenderLayer crash

Error trace copied below:

Uncaught TypeError: Cannot read property 'get' of undefined
    at TextRenderLayer._forEachCell (TextRenderLayer.js:51)
    at TextRenderLayer._drawBackground (TextRenderLayer.js:101)
    at TextRenderLayer.onGridChanged (TextRenderLayer.js:164)
    at eval (Renderer.js:166)
    at Array.forEach (<anonymous>)
    at Renderer._renderRows (Renderer.js:166)
    at RenderDebouncer._innerRefresh (RenderDebouncer.js:31)
    at eval (RenderDebouncer.js:26)

This only started with v3.11.0, this did not happen in v3.10.1 (I’ve gone back and tested the same sample on v3.10.1).

Something of note is that this is only an issue when you have a long text gets printed to the terminal and then you resize the terminal smaller, and then resize it bigger. Another interesting behavior is that this ONLY occurs if you resize both rows AND columns, if you simply resize columns, without resizing rows, it does not crash the render (simply resizing rows also does not crash).

I would imagine it’s probably something introduced by text-wrap feature, but I’m not too sure.

Thanks in advance to anyone looking into this!

Code snippet to play with: https://codesandbox.io/s/4jnl8qxxn4

[Tyriar]

Reduced repro in demo:

1. Run in console: term.resize(40,40)
2. Paste console core fd full mqueue null ptmx pts random stderr stdin stdout tty urandom zero and press enter
3. Run in console: term.resize(100,100)
4. Run in console: term.resize(200,200)

This throws because lines.length === 198 (not 200)

[thenengah]

Also running into this issue. [UPDATED] na, actually mine is a little different. But it is on resize.

I downgraded to 3.10.0 and that fixed the issue. Will revisit this issue after this bug is addressed as it might affect the issue I was facing.