A lot of output locks up then crashes Hyper

[Tyriar]

Tested under Ubuntu 16.04.

When running:

time ls -lR /usr

Hyperterm locks up to 1 frame every few seconds and crashes (turns all black then all white) shortly afterwards.

By comparison, gnome-terminal runs in:

real    0m6.967s
user    0m1.372s
sys 0m2.444s

This is almost certainly an issue with hterm and a use case they haven't optimized around. As an aside, we've worked a bit to get this usable on xterm.js which runs it in around 10 seconds but there are still improvements to be made.

[timothyis]

@Tyriar, is this still the case?

[ppot]

@codetheory yes 😞

[nkkollaw]

I don't know if I'm having the same issue.

With commands that generate a lot of output, Hyper will stop responding.

Memory usage keeps going up, and then it just stops responding.

This command will do that:

time ls -lR /usr

[kevinelliott]

This is affecting me too.

[nadim]

Had to switch to an alternate terminal today when this popped up. Grepping consistently crashes the program (Hyper Helper = 100% CPU usage) and makes me lose all tabs. This is a deal breaker.

[jsullivan]

I can second this. Deal breaker for me, too. Had to sadly switch back to Terminal.app today, much as I love Hyper.js.

[emirotin]

Somehow related I assume: hangs when doing npm install of a moderate size (nothing crazy, 20-30 direct dependencies) on macOS (MBP 2017, SSD, 16GB RAM).
Eventually it gets back to normal, but until then it's completely unresponsive.

[danishmughal]

Definitely a deal breaker - I want to use hyper but it's impossible to do so when it doesn't really seem to be able to handle giant outputs/logs in a day-to-day dev environment. Hoping some more progress is made on the performance side of things.

[bntzio]

This is happening to me too, hyper freezes all the time after I do npm installs, what could it be?