[mythtv-users] Anyone else? - Reproducible frontend crash playing HD MPEG2

[David George]

On 12/18/2007 01:16 AM, William Price wrote:
> Hello.  I'm new to the list and I'm looking for other users who share my 
> problem.  My frontend will segfault on certain files, always at the same 
> location.  It has happened so far on two different HD recordings from 
> two different channels and is 100% reproducible.  I've tested this on 
> two different frontend boxes, both running 64-bit Fedora 7.  Aside from 
> this, Myth has been rather stable.
>
> Any help or redirection is appreciated; what follows is the tail of my 
> console error out:
>
> [mpeg2video @ 0x2aaaac4a6040]invalid mb type in P Frame at 3 39
> [mpeg2video @ 0x2aaaac4a6040]invalid mb type in P Frame at 29 40
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 63 39
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 19 41
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 28 40
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 56 40
> [mpeg2video @ 0x2aaaac4a6040]mb incr damaged
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 60 41
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 3 42
> [mpeg2video @ 0x2aaaac4a6040]mb incr damaged
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 62 42
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 35 43
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 7 44
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 60 43
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 50 44
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 42 44
> [mpeg2video @ 0x2aaaac4a6040]ac-tex damaged at 77 44
> [mpeg2video @ 0x2aaaac4a6040]end mismatch left=55 81AC
> [mpeg2video @ 0x2aaaac4a6040]Warning MVs not available
> [mpeg2video @ 0x2aaaac4a6040]end mismatch left=54 8196
> [mpeg2video @ 0x2aaaac4a6040]Warning MVs not available
> [mpeg2video @ 0x2aaaac4a6040]end mismatch left=55 81AC
> [mpeg2video @ 0x2aaaac4a6040]Warning MVs not available
> [mpeg2video @ 0x2aaaac4a6040]end mismatch left=54 8196
> Segmentation fault
>   

What version are you running?  Are you capturing OTA, QAM, firewire, 
something else?  I didn't see this back when I was running 0.20, but 
with SVN trunk since I switched in Aug I get this once in a while with 
OTA capture.  In my case its because the signal from the stations around 
here tends to fluctuate and it appears that ffmpeg may not be as robust 
as earlier versions.  Been waiting for svn to settle down a little and 
do some more in depth testing once I had some time.  In the meantime, 
when I replay the file I just get near where I was and hit ok to save a 
bookmark and then forward 30 seconds to try to skip the bad stuff.  
Usually works.

Like you, in my case it is the frontend that crashes.  The backend keeps 
on chugging.

-- 
David