Opened 4 years ago

Closed 4 years ago

#4818 closed defect (fixed)

ffmpeg reporting i/o error, ffplay will never stop playing the file

Reported by: jose1711 Owned by:
Priority: minor Component: avformat
Version: git-master Keywords: dvvideo
Cc: Blocked By:
Blocking: Reproduced by developer: yes
Analyzed by developer: no

Description

Summary of the bug:
How to reproduce:

% ffmpeg -v 9 -loglevel 99 -i io_error_cant_stop_playing.dv -an -vcodec copy /tmp/test.dv
..
Press [q] to stop, [?] for help
io_error_cant_stop_playing.dv: Input/output errorize=  117000kB time=00:00:33.28 bitrate=28800.0kbits/s    
No more output streams to write to, finishing.
..
% ffplay /tmp/test.dev (or crash.dv) - never stops
% ffmpeg -version
ffmpeg version 2.7.2 Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 5.2.0 (GCC)
configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-avisynth --enable-avresample --enable-fontconfig --enable-gnutls --enable-gpl --enable-libass --enable-libbluray --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libv4l2 --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-shared --enable-version3 --enable-x11grab
libavutil      54. 27.100 / 54. 27.100
libavcodec     56. 41.100 / 56. 41.100
libavformat    56. 36.100 / 56. 36.100
libavdevice    56.  4.100 / 56.  4.100
libavfilter     5. 16.101 /  5. 16.101
libavresample   2.  1.  0 /  2.  1.  0
libswscale      3.  1.101 /  3.  1.101
libswresample   1.  2.100 /  1.  2.100
libpostproc    53.  3.100 / 53.  3.100

file in question plays fine in vlc and mplayer, it has been uploaded to a pc from a camera using kinodv (through firewire). i made a smaller sample with dd and uploaded it to ffmpeg ftp (io_error_cant_stop_playing.dv).

when converting the file with mencoder, it does not report any io related error but the resulting file again does not stop playing in ffplay.

Attachments (1)

console_output.txt (5.2 KB) - added by jose1711 4 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 4 years ago by cehoyos

  • Component changed from avutil to undetermined
  • Keywords infinite play input output error io removed
  • Priority changed from important to normal

Unfortunately, I don't understand the issue you are reporting (I am not a native speaker).

Please test current FFmpeg git head and please provide the command line that allows to reproduce your issue together with the complete, uncut console output.
Finally, please explain your issue: Something like "I converted the provided sample with ffmpeg and the output file is 100 seconds long but I expected it to be five minutes".

(Maybe related to bug 329.)

comment:2 Changed 4 years ago by jose1711

with today's git:

command used:
ffmpeg -v 9 -loglevel 99 -an -i io_error_cant_stop_playing.dv -vcodec copy /tmp/test2.dv

console output:
attached

resulting file (/tmp/test2.dv):

  • produces i/o error message on successive ffmpeg conversion (/tmp/test2.dv as a source)
  • ffplay does not stop playing at 102nd second as expected, the timer continues, video becomes a still picture

Changed 4 years ago by jose1711

comment:3 Changed 4 years ago by cehoyos

  • Component changed from undetermined to avformat
  • Keywords dvvideo added
  • Priority changed from normal to minor
  • Reproduced by developer set
  • Status changed from new to open
  • Version changed from 2.7 to git-master

Patch sent, please test ffplay -autoexit.

comment:4 Changed 4 years ago by jose1711

autoexit works (video is terminated). also, the real reason behind this bugreport is not really the possibly harmless i/o error or ffplay not terminating but a problem that - according to vapoursynth developers - lies with some libav core library: http://forum.doom9.org/showthread.php?p=1733283#post1733283

to cite him: "The crash seems to happen somewhere deep inside libav so I'm really stuck on this one."

comment:5 Changed 4 years ago by richardpl

What crash?, this issue is about wrong error code returned at eof.

comment:6 Changed 4 years ago by jose1711

the crash only manifests itself in vapoursynth - that is where the initial bug report went to. the vapoursynth dev (contacting me privately) believes there's a problem with libav. now that i think of it i may have done an incorrect assumption that libav is related to ffmpeg. is this the case?

comment:7 Changed 4 years ago by cehoyos

  • Resolution set to fixed
  • Status changed from open to closed

Should be fixed in 3eae98c1ac705d3f820a1800e81960146a80c61c

Nothing in the backtrace you provided indicates a FFmpeg bug. If you have more information, please open a new ticket.

Note: See TracTickets for help on using tickets.