Open jsun-sun opened 4 years ago
Why did you close the issue?
Caused by my laptop turned into power-saving mode. Every time when it started showing screensaver, the same error message popped up.
On Mon, 24 Feb 2020 at 04:56, Sebastian Pfitzner notifications@github.com wrote:
Why did you close the issue?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/JunoLab/atom-ink/issues/263?email_source=notifications&email_token=AGBZNIMEEFJCGVCRDTJLPLDREOKVHA5CNFSM4KZ7UBL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMXGI4I#issuecomment-590242929, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGBZNIIAERS3GUMOXFDEEI3REOKVHANCNFSM4KZ7UBLQ .
Ah, good to know. I'll reopen the issue since it seems like we could handle this more gracefully.
Some background on this - the error is actually a safety measure by xterm.js to avoid OOM. This would happen, if xterm.js gets more than 50MB in the write buffer pending, which should never be the case (xterm.js gets unusable much earlier). To avoid it, plz see https://xtermjs.org/docs/guides/flowcontrol/ on how to implement flow control. Sadly we cannot blueprint this in a general way, as it needs backend preparations.
[Enter steps to reproduce:]
Atom: 1.44.0 x64 Electron: 4.2.7 OS: Mac OS X 10.15.3 Thrown From: ink package 0.12.2
Stack Trace
Uncaught Error: write data discarded, use flow control to avoid losing data
Commands
Non-Core Packages