UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10895.56.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.95 Safari/537.36
Platform: 10895.56.0 (Official Build) stable-channel sentry

Steps to reproduce the problem:
Use hterm either locally (through crostini) or remotely (secure ssh). Then type any command that generates lots of output (i.e. find /usr)

The application will hang and it will take a very long time before stdin is usable again.

What is the expected behavior?
The same thing in a regular terminal (xterm or gnome-terminal) will finish in less than 1 second and allow stdin input almost instantaneously.

What went wrong?
hterm can't keep up with the rate of output, but instead of discarding it chooses to display everything.

This may be due to the lack of a scrollback buffer limit. From a user standpoint it would be much better to simply discard all the output and display an error message that requires the user to refresh the screen, than to wait 5-10 minutes for the output to complete or be forced to hard close the application.

Did this work before? No 

Chrome version: 69.0.3497.95  Channel: stable
OS Version: 10895.56.0
Flash Version: 

Now that hterm is used in other places (crostini) I think this bug becomes more relevant.

Searching online it seems this issue is well known. External projects have switched away from hterm (to xterm.js) to solve the issue, see https://github.com/zeit/hyper/issues/94

However this is likely not a real alternative for chromeos, so it would be best to fix this bug instead hterm