kkroening/ffmpeg-python

BrokenPipeError doesn't explain the cause: disk full

to7m opened this issue · 1 comments

to7m commented

When using a pipe to write raw audio/video, if the output file can't be written to anymore due to the disk filling up, then a BrokenPipeError is raised. It would be helpful if this were caught and converted to a more descriptive error.

BrokenPipeError can have many causes, only one of which is a full disk (can also be caused by OOM, process kill, etc). It’s likely not feasible to add a disk space check because ffmpeg doesn’t know ahead of time how large the output object will be.

If you want a disk space check, it is probably more effective and easier if you add it in your own code downstream.