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
Fatal error in api.cc #95
Comments
I'll take a look at this in the evening. |
Thank you. This occurred on 7.0.0. I want to avoid rolling back the node version on my server is possible. |
I know node-jitterbuffer had some deprecation warning a while back, but when I tried debugging that I had trouble getting the thing to compile in my environment. No idea what caused that - then I forgot about it. The stack fortunately has the line numbers for node-jitterbuffer so I'll take a look at how to fix that. I'm guessing that's the reason this is happening now. |
Found the issue in node-jitterbuffer. Fixed it there (and in node-celt). |
working now, thanks you're awesome. |
I might disagree with that given Node started warning about this in 6.0.0 and it was reported in August by notthetup in #92 but I never got around fixing it until it broke. But I'm glad someone thinks that way. Thanks! :) |
I'm not sure if this is something that broke in newer versions of node / npm installs, but I've been getting this error constantly.
The text was updated successfully, but these errors were encountered: