I have tested using gplay and I can duplicate the same issue with it. If I keep seeing forward and backward for a few minutes I can get the video to hang and gplay quits as follows:
0:01:38.756373994 3882 0xc1d88 WARN aiurdemux aiurdemux.c:3900:aiurdemux_push_pad_buffer: Pad audio push error type -2
0:01:38.758524661 3882 0x15700 WARN aiurdemux aiurdemux.c:1461:gst_aiurdemux_perform_seek: Seek to 0:19:33.000000000.
0:01:38.763291661 3882 0xc1d88 WARN aiurdemux aiurdemux.c:1287:aiurdemux_send_stream_newsegment: Pad audio: Send newseg 0:19:32.938434000 first buffer 0:19:32.561267000
0:01:38.768295994 3882 0xc1d88 WARN aiurdemux aiurdemux.c:1276:aiurdemux_send_stream_newsegment: Timestamp unexpect, maybe a core parser bug!
0:01:38.768450661 3882 0xc1d88 WARN aiurdemux aiurdemux.c:1287:aiurdemux_send_stream_newsegment: Pad video: Send newseg 0:19:32.938434000 first buffer 0:19:33.272100000
0:01:38.794804328 3882 0x30b383d0 WARN bin gstbin.c:2380:gst_bin_do_latency_func:<playbin0> did not really configure latency of 0:00:00.000000000
full screen size:1280x1024
0:01:38.798674327 3882 0x30b383d0 WARN mfw_v4lsink mfw_gst_v4l.c:1422:mfw_gst_v4l2_display_init: Wrong display width information
0:01:38.798795994 3882 0x30b383d0 WARN mfw_v4lsink mfw_gst_v4l.c:1426:mfw_gst_v4l2_display_init: Wrong display height information
[Playing ][Vol=01][00:19:33/00:21:44][fps:2] Aborted by signal Interrupt...
I did not have it in the debugger to get any other info but I thought I would post the information. The following message comes out a lot with GST_DEBUG setup even when things work but I am not concerned with the audio at this point.
0:01:38.756373994 3882 0xc1d88 WARN aiurdemux aiurdemux.c:3900:aiurdemux_push_pad_buffer: Pad audio push error type -2
Brian