Hangs/Slows down siginificantly when dealing with streaming logs

[klevermonicker]

• I am on the latest Hyper.app version

• I have searched the issues of this repo and believe that this is not a duplicate

• OS version and name: OSX - High Sierra (10.13.1)

• Hyper.app version: 2.1.1 (canary)

• Link of a Gist with the contents of your .hyper.js: https://gist.github.com/klevermonicker/1fd989dc39c39eed25f88a0cb1521d15

• Relevant information from devtools N/A

• The issue is reproducible in vanilla Hyper.app: Is Vanilla

Issue

Fairly easy to reproduce, when I'm looking through say our elk stack and trying to find out what happened to logstash and looking through log files, catting those through hyper slows it to a crawl and it's unable to keep up with the output and locks up the terminal where I have to either wait for 2-3 minutes or force quit out of the application.

I tried moving to canary to see if it was addressed there and it's not.

[lucasqueiroz]

It happens to me too.
For example, when running a docker project, or building something with maven, it takes a long time.

[farfromrefug]

Same thing here. IT s actually really bad because sometimes it takes 30s to show the updated logs. Which makes it hard to work with.

[richrace]

I've noticed that output from processes/logs etc. is slow when running certain Plugins.

The following code output is very slow when I have hypercwd and hyper-statusline enabled. If I remove both these plugins, I do not experience any slow down in output.

Still happens in Canary 11.

for ((i=1; i<=10000; i++)); do
   echo $i
done

Related issues:
hharnisc/hypercwd#37
henrikruscon/hyper-statusline#69

[countergram]

I removed all plugins and still am experiencing major slowdowns with lots of output. E.g. running the yes utility locks the UI (unresponsive to keyboard and mouse input).

[chabou]

@countergram Which Hyper version do you use?

[countergram]

Hyper 1.4.8 (stable) on MacOS Sierra, also tried building canary, same deal.

[x3b3ch3]

Same issue for me Hyper 2.0.0 (stable), no plugin, Mac OS High Sierra 10.13.4, MacBook Pro, 16Go. RAM.
Try `cat /dev/urandom' Mac OS, You will get a realistic picture of the problem.
Maybe some options in .zshrc inherited from iterm2??

[danielkalen]

Here is a demonstration of a side-by-side comparison of hyper(left) and iterm(right). After some input, I tried hitting ctrl+c on both terminals and you can see how hyper couldn't even process my input until like 15 secs later (and it seems like only 3 ^Cs were picked up, but I sent that command at least 25 times).

This renders hyper practically useless for serious work... Only reason I'm still keeping Hyper as my main terminal because I know this will be fixed soon :)

[danielkalen]

Mind you that this was tested on hyper 2.1.0 canary

[MatthiasWinkelmann]

I just tried this with:

ruby -e "10000.times {|i| puts i }"

...and the output was pretty much instant. Can you run that and see if it gives you any problems, or otherwise create a small test case?

As mentioned in #687 (comment), Hyper's speed has improved rather dramatically, but if it's a top priority for your work, you will probably be happier with the native Terminal.app for the foreseeable future.

Responses to interrupts (ctrl+c) being delayed is a known problem (see #555, #1121, and #1484), but may actually require changes in https://github.com/xtermjs/xterm.js or https://github.com/Microsoft/node-pty.

[danielkalen]

@MatthiasWinkelmann I tried this command and the exact same thing is happening i.e. it hangs like a mofo. Given that you cannot replicate this issue maybe this is something unique to my env i.e. a certain plugin probably generating errors. I'll check it out and report back

[danielkalen]

Although I had a bunch of errors on an existing terminal session originating from hyper-statusline and seemingly internal code.

But I started a new window and ran the command and here is what I've got (this is a gif 30fps):

[richrace]

@danielbayerlein See henrikruscon/hyper-statusline#69

[danielkalen]

@richrace confirmed! Removed hyper-statusline and it's fixed!

[joshbetz]

Related #2502

[mabdelfattah]

@richrace @danielkalen +1 for disabling hyper-statusline