-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node is freezing #15
Comments
Thanks for reporting, I'll investigate this over the next days |
Did the first steps to debug this, seems like |
Great, it felt like a infinite loop :-) Looking forward to a fix, thank you man. |
Did a quick dirty test setup in svg-term // svg-term/index.tsx#L81
console.log('load');
const cast = load(json, options.width, typeof options.height === 'number' ? options.height + 1 : undefined);
console.log('load', process.hrtime(start)); logs |
Looks like it happens with the all new casts :-( UPD: it's not true, not all casts affected |
@bunopus That’s not what I experience in daily usage. Could you provide the version of your asciinema cli and links to affected uploaded casts? |
@marionebl it's very strange
I have two casts with almost the same content, but one is working, second - not. 🤔 |
Spent some more time on this.
What jumped at me is the big dimensions. Forcing down the screen buffer size leads to notable speed increases:
I'll create an issue with asciinema about this. For the time being you can force the screen buffer down via
|
Hello,
svg-term works perfect on my machine with the given
113643
example cast.There seems to be an issue with new formats. I had to download my new cast in the
version 1
syntax assvg-term
told me that onlyversion 1
andversion 2
syntax are supported.Watch cast: https://asciinema.org/a/znqFxSzM9CmIJINrmn2IzPX5g
Download JSON: https://asciinema.org/a/znqFxSzM9CmIJINrmn2IzPX5g.cast?dl=true
Setup
svg-term: 2.0.3
NodeJS: 8.7.0
NPM: 5.6.0
OS: Ubuntu 17.04
Command
Issue
The terminal and sometimes my whole machine is freezing - there is no way to cancle it using
CTRL+C
. No output is being processed.The text was updated successfully, but these errors were encountered: