-
Notifications
You must be signed in to change notification settings - Fork 38
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
Segmentation fault (core dumped) #10
Comments
Could you be more specific? Here are some details that might help:
|
Sorry, here is the information:
|
Did you add it manually? Or did you run the I noticed there is a I can't reproduce this exactly, however I have successfully tested this on an Ubuntu 18.04 machine with node v14.15.4 and npm v6.14.10 (you could try these specific versions but I highly doubt it is a version issue). |
You could try adding the following piece of code at the beginning of
|
Thank you very much for your support.
I add it by the command
I can hear the
I also try upgrading node to latest version ( node: 'v15.6.0', npm: '7.4.0' ) but still not work.
Here is the log when running with node v15.6.0, npm 7.4.0 I guess something went wrong with opus decoder
|
I tried with a fresh install on a fresh Ubutu 20.10 VM. Steps:
|
You are right, unfortunately, something is wrong with your environment, the recorder crashes at startup :(
I'm sorry this is my fault, I should have updated the
|
Thank you. I will report it to the library repo.
|
As I said, I cannot help you with these errors because If you're still struggling, I suggest you give docker a shot. Docker containers should work anywhere ;) |
i have this problem, "Segmentation fault (core dumped)". I run docker container, Dockerfile this project. |
Unfortunately there isn't much I can do here as I am unable to reproduce this at my end. You could try following the previous comments to debug yourself, if the problem is with |
Did you try to use a browser based discord client? Because this error happens only using browser client. For aondroid client it works fine |
Just tested this on firefox v87.0, node v14.15.4 and npm 6.14.10 with absolutely no issues. Are you sure about this? |
@chebro Can you try with chrome browser ? |
@chebro I found the problem ! Somehow when I did I could see it because after installation, the file So to fix it, I had to install the specific version manually :
|
I got an error with fresh install and run
The text was updated successfully, but these errors were encountered: