iopkc.blogg.se

Heroku fluent ffmpeg
Heroku fluent ffmpeg






heroku fluent ffmpeg heroku fluent ffmpeg heroku fluent ffmpeg

If anybody has any ideas what the problem could be about, please let me know! I can also provide more info if needed. (/app/node_modules/fluent-ffmpeg/lib/processor.js:197:11)Īpp: at Socket.emit (node:events:539:35)Īpp: at Pipe. (/app/node_modules/fluent-ffmpeg/lib/processor.js:180:22)Īpp: at ChildProcess.emit (node:events:527:28)Īpp: at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)Īpp: Emitted 'error' event on FfmpegCommand instance at:Īpp: at emitEnd (/app/node_modules/fluent-ffmpeg/lib/processor.js:424:16)Īpp: at endCB (/app/node_modules/fluent-ffmpeg/lib/processor.js:544:13)Īpp: at handleExit (/app/node_modules/fluent-ffmpeg/lib/processor.js:170:11)Īpp: at Socket. The application itself is a Discord bot (using discord.js), which I had combined with fluent-ffmpeg to handle some smaller video conversions (and then upload them as an attachment to a message) - which worked fine until just recently.īut now it suddenly crashes whenever the app tries to run the ffmpeg process, here's the error log: app: Spawned ffmpeg with command: ffmpeg Īpp: throw er // Unhandled 'error' eventĪpp: Error: ffmpeg was killed with signal SIGSEGVĪpp: at ChildProcess. So anyway, let me describe the problem situation:

heroku fluent ffmpeg

This problem does not occur locally too, only when deployed on Heroku, and what makes it even weirder is that it used to run fine until just yesterday. Using Pipenv will generate runtime.txt based on python-version at build time.First of all, please forgive me if this is the wrong place to ask this question - unfortunately, my Google Searches for this problem have left me empty-handed. To specify your python version, you also need a runtime.txt file - unless you are using the default Python runtime version.Ĭurrent default Python Runtime: Python 3.6.7Īlternatively, you can provide a setup.py file, or a Pipfile. Remote: Procfile declares types -> (none)Ī requirements.txt must be present at the root of your application's repository to deploy. Remote: Installing collected packages: Werkzeug, click, MarkupSafe, Jinja2, itsdangerous, flask Remote: Collecting flask (from -r /tmp/build_c2c067ef79ff14c9bf1aed6796f9ed1f/requirements.txt (line 1)) Remote: -> Installing requirements with pip My-application requirements.txt runtime.txt








Heroku fluent ffmpeg