bug: ffmpeg-static Crashes When Accessing Remote HTTPS Video URLs (Likely Networking Bug)

[mena234]

ffmpeg-static version

ffmpeg-static@5.2.0

Node.js version

v18.19.1

operating system and/or environment

• using operating system Windows 11

What happened?

The ffmpeg-static binary crashes with a segmentation fault (SIGSEGV) when attempting to access remote video files via HTTPS. This happens even with the simplest command:

ffmpeg -i "https://cdn.pixabay.com/video/2025/04/27/275052_large.mp4"
No encoding, filtering, or processing is involved — the crash occurs at the initial input access phase.

Reproduction Steps
Install ffmpeg-static in a Node.js environment.

Attempt to run:

./node_modules/ffmpeg-static/ffmpeg -i "https://cdn.pixabay.com/video/2025/04/27/275052_large.mp4"
Observe segmentation fault.

Diagnostic Findings
To isolate the issue, the video was downloaded manually using curl:

curl -L -o remote_video.mp4 "https://cdn.pixabay.com/video/2025/04/27/275052_large.mp4"
Then processed locally:

./node_modules/ffmpeg-static/ffmpeg -i remote_video.mp4
Result: This succeeded, confirming that the crash is specific to FFMPEG’s internal networking stack.

[Jack-the-Pro101]

This is also a problem on Linux. Additionally, the same problem occurs with John Van Sickle's 7.0.2 static build.

Interestingly, this does not occur with the FFMPEG 6.1.1 package on Ubuntu 24.04.2 LTS.

[rkjaran]

This is also a problem on Linux. Additionally, the same problem occurs with John Van Sickle's 7.0.2 static build.

Interestingly, this does not occur with the FFMPEG 6.1.1 package on Ubuntu 24.04.2 LTS.

 Notes:  A limitation of statically linking glibc is the loss of DNS resolution. Installing
        nscd through your package manager will fix this.

from the readme (https://johnvansickle.com/ffmpeg/release-readme.txt)