-
Notifications
You must be signed in to change notification settings - Fork 718
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
Error: ffmpeg was killed with signal SIGSEGV #66
Comments
I am trying to take a screenshot out of a video and facing the same issue. Did you find the solution? |
Unfortunately not yet. |
i have same issue,ffmpeg was killed with signal SIGSEGV,have you fixed it? |
I haven't looked at the issue since that time, unfortunately I don't have any new insights on it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First of all, thank you for the great buildpack repo!
Heroku kills the ffmpeg process for some larger files and I'm not sure what the issue is.
~5mb .mp4s work well but 60mb .mov files are giving me errors.
We use 2GB ram on Heroku. A local ffmpeg process on my machine for the larger file goes up to ~900MB ram and runs successfully, so that should not be an issue.
I've reached out to Heroku support, but since it's not an official buildpack, they redirected me to ask in the buildpack repo directly.
Full error stack trace:
The ffmpeg command I'm running:
The text was updated successfully, but these errors were encountered: