Closed sorenrasmussen closed 4 years ago
I can reproduce this on Windows when I run it from the command line. When I run it in my IDE and invoke a KeyboardInterrupt, the error does not happen. In the latter case I know that only the main thread is interrupted. I therefore suspect that the helper threads for the ffmpeg (one that reads frames and one that reads stderr) are interrupted. We should prevent this from happening.
Moved this issue to the new imageio_ffmpeg
repo.
I tried this: https://stackoverflow.com/a/39174578/2271927 but the solution for Windows does not seem to work.
Looking into this now and having a facepalm moment when I realized it's the ffmpeg process stopping because the interrupt propagates to the subprocesses 🤦♂
After a manual KeyboardInterrupt ([Ctrl]+[c]), reading a frame with (index > 0) causes an FFMPEG error.
System: Imageio 2.4.1 Python 3.6.5 FFMPEG 3.2.4 Linux 64bit