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

Failed to write frame to ffmpeg: Broken pipe (os error 32) #228

Open
louis030195 opened this issue Aug 26, 2024 · 11 comments
Open

Failed to write frame to ffmpeg: Broken pipe (os error 32) #228

louis030195 opened this issue Aug 26, 2024 · 11 comments

Comments

@louis030195
Copy link
Collaborator

ERROR screenpipe_server::video] Failed to write frame to ffmpeg: Broken pipe (os error 32)

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

Copy link

algora-pbc bot commented Aug 26, 2024

💎 $100 bounty • Screenpi.pe

Steps to solve:

  1. Start working: Comment /attempt #228 with your implementation plan
  2. Submit work: Create a pull request including /claim #228 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to mediar-ai/screenpipe!

Add a bountyShare on socials

@louis030195
Copy link
Collaborator Author

louis030195 commented Aug 26, 2024

.

@tmahmood
Copy link

Interested about this. Can you describe how to reproduce this error? When this error occurs?

@louis030195
Copy link
Collaborator Author

i have no idea

does not happen frequently, seems random

@tmahmood
Copy link

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.

@louis030195
Copy link
Collaborator Author

@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

@booti386
Copy link

Which operating system? It looks like ffmpeg closes its input stream (crashes maybe?) before receiving all the data.

@louis030195
Copy link
Collaborator Author

@booti386 saw this on linux (some user) and on my mac once

@louis030195
Copy link
Collaborator Author

image

@MinisculeGirraffe
Copy link

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".

@louis030195
Copy link
Collaborator Author

@MinisculeGirraffe probably solving this #194 would be a more long term investment if you want to give a try

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants
@tmahmood @booti386 @louis030195 @MinisculeGirraffe and others