[mythtv-users] Mythfrontend crashing on some videos

[JCA]

I am running MythTV 0.24 under Slackware 13.1 on a four-core Athlon II
X4 processor. I have got at least one video (possibly others) that
predictably crash mythfrontend. The video is an MKV file that was
obtained as the result of processing some video material with
HandBrake 0.9.5, the idea being to deinterlace the original video
material.

The resulting video plays fine under mplayer, which prints out the following:

MPlayer 20100218-4.4.3 (C) 2000-2010 MPlayer Team

Playing AllMKV.mkv.
[mkv] Track ID 1: video (V_MPEG4/ISO/AVC), -vid 0
[mkv] Track ID 2: audio (A_AAC), -aid 0, -alang und
[mkv] Track ID 3: audio (A_AC3), -aid 1, -alang und
[mkv] Will play video track 1.
Matroska file format detected.
VIDEO:  [avc1]  1440x1056  24bpp  29.970 fps    0.0 kbps ( 0.0 kbyte/s)
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
==========================================================================
Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding)
FAAD: compressed input bitrate missing, assuming 128kbit/s!
AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000->192000)
Selected audio codec: [faad] afm: faad (FAAD AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
AO: [oss] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
Movie-Aspect is 1.82:1 - prescaling to correct movie aspect.
VO: [xv] 1440x1056 => 1920x1056 Planar YV12
A: 141.3 V: 141.1 A-V:  0.155 ct:  0.083   0/  0 86%  5% 181.8% 13 0
Exiting... (Quit)

When playing it from mythfrontend, using the internal player,
mythfrontend crashes and the following diagnostic can be found as part
of the output from dmesg:

mythfrontend[19740]: segfault at 9f9f8000 ip b64a1ad0 sp 9d238048
error 4 in libmythavcodec.so.52.86.1[b605b000+58e000]

It would seem that the scaling that mplayer reports above, from
1440x1056 to 1920x1056, is connected with it. Anyway, is this a known
problem with the internal player? Are there any ways around it? I
mean, other than using mplayer instead (which has issues of its own,
at rate)?