jonathanong / heroku-buildpack-ffmpeg-latest

A Heroku buildpack for ffmpeg that always downloads the latest static build
MIT License
361 stars 725 forks source link

Error: ffmpeg was killed with signal SIGSEGV #66

Open sergejkurbanov opened 1 year ago

sergejkurbanov commented 1 year ago

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:

Error: ffmpeg was killed with signal SIGSEGV
at ChildProcess.<anonymous> (/app/node_modules/fluent-ffmpeg/lib/processor.js:180:22)
at ChildProcess.emit (node:events:369:20)
at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)

The ffmpeg command I'm running:

ffmpeg(file.url)
  .inputOption('-headers', `Authorization:\ Bearer\ ${authKey}`)
  .complexFilter([
    '[0:v] scale=320:-1:flags=lanczos,split [a][b]',
    '[a] palettegen [p]',
    '[b][p] paletteuse',
  ])
  .fps(10)
  .on('end', () => resolve())
bilalaslam777 commented 1 year ago

I am trying to take a screenshot out of a video and facing the same issue. Did you find the solution?

sergejkurbanov commented 1 year ago

Unfortunately not yet.

nicky132 commented 1 year ago

Unfortunately not yet.

i have same issue,ffmpeg was killed with signal SIGSEGV,have you fixed it?

sergejkurbanov commented 1 year ago

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.