You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Bun's child_process.spawn to invoke FFmpeg, I observed that when FFmpeg parameters specify a custom input pipe (e.g., -i pipe:3) and data is written to the corresponding stdio[3], FFmpeg does not receive the data, resulting in no output and potential process blocking. However, the same code works as expected in the Node.js environment. This suggests that Bun's spawn implementation may have an issue handling additional pipes beyond the standard stdin, stdout, and stderr.
Bun vs NodeJS(v20.14.0)
Bun:
NodeJS:
The text was updated successfully, but these errors were encountered:
What version of Bun is running?
1.2.4
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What steps can reproduce the bug?
What is the expected behavior?
The following code will be triggered repeatedly:
Console output:
What do you see instead?
The following code is not triggered:
Additional information
Problem Description
When using Bun's child_process.spawn to invoke FFmpeg, I observed that when FFmpeg parameters specify a custom input pipe (e.g., -i pipe:3) and data is written to the corresponding stdio[3], FFmpeg does not receive the data, resulting in no output and potential process blocking. However, the same code works as expected in the Node.js environment. This suggests that Bun's spawn implementation may have an issue handling additional pipes beyond the standard stdin, stdout, and stderr.
Bun vs NodeJS(v20.14.0)
Bun:
NodeJS:
The text was updated successfully, but these errors were encountered: