Skip to content
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

ffprobe hangs #1089

Open
2 of 3 tasks
laggingreflex opened this issue Dec 11, 2020 · 0 comments · May be fixed by #1090
Open
2 of 3 tasks

ffprobe hangs #1089

laggingreflex opened this issue Dec 11, 2020 · 0 comments · May be fixed by #1090

Comments

@laggingreflex
Copy link

Version information

  • fluent-ffmpeg version: 2.1.2
  • ffmpeg version: 4.2
  • OS: Win10

Code to reproduce

await ffprobe('input.mp4')

This sometimes never resolves.

(note: if the problem only happens with some inputs, include a link to such an input file)

It's unpredictable. Sometimes it works with same files.

Expected results

Should work as usual.

Observed results

Sometimes ffprobe never resolves

Checklist

  • I have read the FAQ

  • I tried the same with command line ffmpeg and it works correctly (hint: if the problem also happens this way, this is an ffmpeg problem and you're not reporting it to the right place)

    running ffprobe.exe via command-line on same files works 100% of the time without fail. Only when running ffprobe() from fluent-ffmpeg does the problem ocurr

  • I have included full stderr/stdout output from ffmpeg

    Not sure how to get this but I'm guessing it's normal.

I think the issue is that the process (ffprobe.exe spawned from node) is for some reason not exiting (ever), and thus leaving the code in a hung state.

I've come up with a hacky solution that makes it work in the linked PR as a demo where problem exists.

@laggingreflex laggingreflex linked a pull request Dec 11, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant