[CRASH] mythcommflag segfaults on HD recording

[Ken Emerson <kenneth.emerson@…>]

Four segfaults over past 3 days out of 28 recordings.

Backtrace attached

Log File:

274497 commflag 5 0 2010-10-13 22:12:24 mythtv Commercial Detection Finished "Law & Order: Los Angeles":"Harbor City" recorded from channel 1061 at 2010-10-13T21:00:00 (139 commercial break(s))

9 274496 commflag 5 0 2010-10-13 22:12:13 mythtv Commercial Detection Starting "Law & Order: Los Angeles":"Harbor City" recorded from channel 1061 at 2010-10-13T21:00:00

MythTV Version : 26737 MythTV Branch : trunk Network Protocol : 63 Library API : 0.23.20100917-1 QT Version : 4.6.2 Options compiled in:

linux debug using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl u

sing_bindings_python using_directfb using_dvb using_firewire using_frontend using_hdhomerun using_h dpvr using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc using_mheg using_opengl_vi deo using_opengl_vsync using_qtdbus using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_ xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_mythtranscode using _opengl using_vdpau using_ffmpeg_threads using_live using_mheg

[beirdo]

Looks like you have a bad H.264 recording.

[anonymous]

When I looked at the backtrace, I also saw the reference to H.264; however, the channel ID is 1061 which, I'm assuming, means it used video source #1 which is SD local broadcast. This video source is tied to either my HVR-1800 or my HD-HR both of which produce mpeg-2 files. So why the reference to H.264 (which to my understanding only applies to my HD-PVR).

[Ken Emerson <kenneth.emerson@…>]

This problem surfaced again last night on an NBC program. Backtrace is similar to the one previously attached. As an added point of interest, I rescheduled the the commflag job and it completed normally finding five commercial breaks.

[beirdo]

Is this still an issue in 0.24-fixes or master? A lot of code changes have occurred since this was reported, and if it's not repeatable with newer versions of mythtv (and hence ffmpeg libraries, where this is crashing), then we should close this.

[cpinkham]

Closing this ticket as requested update not received in 4 weeks. If the issue is still happening with 0.24-fixes or current git master, we'll need an updated backtrace and probably a sample of the file.