-
Notifications
You must be signed in to change notification settings - Fork 109
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
Failed to write frame to ffmpeg: Broken pipe (os error 32) #228
Comments
💎 $100 bounty • Screenpi.peSteps to solve:
Thank you for contributing to mediar-ai/screenpipe! |
. |
Interested about this. Can you describe how to reproduce this error? When this error occurs? |
i have no idea does not happen frequently, seems random |
Any debug log? Does this happen to fresh install? Is it fatal? I'm seeing many errors about missing files, but have not seen this one. |
@tmahmood what do you mean missing files? did not see anyone complaining about this for 3-4 days so i think you might just look at solving other issues and maybe it will come up |
Which operating system? It looks like ffmpeg closes its input stream (crashes maybe?) before receiving all the data. |
@booti386 saw this on linux (some user) and on my mac once |
There's no practical way to debug this because you're not pinning a known ffmpeg version with the application. For some reason, ffmpeg is closing it's input stream, so that log is being generated. I could add retry logic so when the input stream is closed it re-creates a new process. But that doesn't exactly solve the root issue here of "It's going to do weird stuff because platform/feature flag/version differences". |
@MinisculeGirraffe probably solving this #194 would be a more long term investment if you want to give a try |
this is a new error, did not exist last week
gotta look at what changed but this error is nondeterminisitc (e.g. sometime just restart and it works) and affects only the screen video encoding
/bounty 50
The text was updated successfully, but these errors were encountered: