[mythtv-users] Failed with exit status 140
Rich West
Rich.West at wesmo.com
Mon Apr 15 18:01:22 UTC 2013
On 04/15/2013 01:44 PM, Karl Newman wrote:
> On Mon, Apr 15, 2013 at 10:22 AM, Rich West <Rich.West at wesmo.com
> <mailto:Rich.West at wesmo.com>> wrote:
>
> Since upgrading to 0.26 and getting the system stabilized, all of my
> commercial flagging jobs are failing with "Failed with exit status
> 140". I've done some googling which suggests that something is
> killing
> off the commflag process, but I cannot find any evidence of that.
>
> The system is a brand new install of Fedora 17 with a 0.26 db upgrade
> over the years. It has plenty of memory and disk space. Because
> everything is being encoded by external boards (hdhomerun, pvr150's),
> the CPU is rather bored, too. The DB tables are all good (nothing
> needing to be repaired).
>
> In looking at the logs:
>
> 1. a majority of the mythcommflag*.log files stop at "Finding
> Logo" with
> no further information.
>
> 2. he remaining ones (only 14 so far), go as far as "CoreContext
> ClassicCommDetector.cpp:536 (go) - 90% Completed @ 52.179 fps."
> and then
> generate:
> Decoder avformatdecoder.cpp:4341 (ProcessAudioPacket) - AFD: Unknown
> audio decoding error
> Decoder avformatdecoder.cpp:4556 (GetFrame) - decoding error
> eno: Unknown error 541478725 (541478725)
> CoreContext main.cpp:941 (FlagCommercials) - Finished, 2 break(s)
> found.
>
> And the web interface lists all of the jobs with the 140 error..
>
> Any ideas as to where to start digging for this one?
>
> Thanks!
> -Rich
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
>
> I think there are some ffmpeg bugs that are causing the majority of
> problems with commflagging in 0.25+. Additionally, there is a race
> condition which causes the commflagging job to abort when it hits
> end-of-file while operating on a recording in progress. The workaround
> for this is to change the setting which prevents commflagging jobs
> from running until the recording is finished. For me, commercial
> flagging was near-perfect in 0.24, but is quite broken since then. I'm
> lucky if it finds one commercial break per show now.
Yikes.. ok.. oh, well. Guess no more commercial detection for me. :(
I just manually ran a commercial flagging job (mythcommflag -f
/video1/1303_20130415162900.mpg) and got:
2013-04-15 13:47:38.550037 C mythcommflag version: fixes/0.26
[0.26.0-7.fc17 (v0.26.0-111-g3944ca9)] www.mythtv.org
2013-04-15 13:47:38.550052 C Qt version: compile: 4.8.4, runtime: 4.8.4
MythTV Commercial Flagger, flagging commercials for:
How to Rock - How to Rock a Statue
Finding Logo*** glibc detected *** mythcommflag: invalid fastbin entry
(free): 0x00007fe410019530 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3b2847c80e]
/lib64/libc.so.6[0x3b284ac5e9]
/lib64/libc.so.6(tzset+0x40)[0x3b284ac8d0]
/lib64/libQtCore.so.4(_ZN5QTime11currentTimeEv+0x20)[0x3b3288a520]
/lib64/libQtCore.so.4(_ZN5QTime5startEv+0x9)[0x3b3288a609]
/lib64/libmythtv-0.26.so.0(_ZN10RingBuffer3runEv+0x6ac)[0x3b4b24234c]
/lib64/libQtCore.so.4[0x3b3287b94c]
/lib64/libpthread.so.0[0x3b28807d14]
/lib64/libc.so.6(clone+0x6d)[0x3b284f199d]
======= Memory map: ========
...
and then it dumped core. :(
Before it did the whole "glibc detected" line, it was cruising along for
a little bit looking like it was going to work (displaying fps & such).
-Rich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130415/e55aa878/attachment.html>
More information about the mythtv-users
mailing list