mythcommflag seg fault - "codec MP3 has 0 channels"

[Andrew Meredith <andrew@…>]

After upgrading from 0.24 to 0.26 I have found that some recordings repeatably crash mythcommflag when trying to do advert detection. It seems to be correlated with recordings that come from the DVB cards, with the following profile according to ffmpeg:

Input #0, mpegts, from '20992_20130227220000.mpg':
  Duration: 01:04:58.89, start: 29964.196356, bitrate: 1876 kb/s
  Program 1 
    Stream #0:0[0x1a21]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p, 544x576 [SAR 32:17 DAR 16:9], 15000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc
    Stream #0:1[0x1a22](eng): Audio: mp2 ([4][0][0][0] / 0x0004), 48000 Hz, stereo, s16, 128 kb/s
    Stream #0:2[0x1a23](eng): Audio: mp3 ([4][0][0][0] / 0x0004), 0 channels, s16 (visual impaired)
    Stream #0:3[0x1a26](eng): Subtitle: dvb_subtitle ([6][0][0][0] / 0x0006)
    Stream #0:4[0x1bb1]: Unknown: none ([11][0][0][0] / 0x000B)

Files recorded prior to the upgrade, with the same ffmpeg profile will crash mythcommflag now, when they didn't under 0.24.

Please note the correlation between the "codec MP3 has 0 channels" and the profile for the "visually impared" treack of "Audio: mp3 ([4][0][0][0] / 0x0004), 0 channels, s16 (visual impaired)"

I have attached a back trace from gdb and can forward a core file if needed.

[Andrew Meredith <andrew@…>]

Log file of gdb run with backtrace

[cpinkham]

I believe this was probably fixed with the latest ffmpeg resync in master by 5c0792da8731 which included a bugfix related to the MP3 0-channels detected issue.

I can't say for sure whether or when this will be back-ported since we are prepping for 0.27.