mythfrontend 0.24 crash after resuming from bookmark

[MarcRandolph]

Tried to resume video at a bookmark

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: mythtv-frontend 2:0.24.0+fixes.20101212.8155c43-0ubuntu0mythbuntu1
ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
Uname: Linux 2.6.32-26-generic i686
Architecture: i386
CrashDB: mythbuntu
Date: Sun Dec 12 09:02:29 2010
ExecutablePath: /usr/bin/mythfrontend.real
Installed_mythtv_dbg: 2:0.24.0+fixes.20101212.8155c43-0ubuntu0mythbuntu1
ProcCmdline: /usr/bin/mythfrontend.real --logfile /var/log/mythtv/mythfrontend.log
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x272bb8b <_int_malloc+491>: mov %edi,0x8(%eax)
 PC (0x0272bb8b) ok
 source "%edi" ok
 destination "0x8(%eax)" (0x0005dc08) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 _int_malloc (av=<value optimized out>, bytes=<value optimized out>)
 _int_memalign (av=<value optimized out>, alignment=16,
 *__GI___libc_memalign (alignment=16, bytes=32776)
 __posix_memalign (memptr=0xa842830c, alignment=384000,
 av_malloc (size=42030016) at libavutil/mem.c:83
Title: mythfrontend.real crashed with SIGSEGV in _int_malloc()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare scanner tape video
XsessionErrors: (polkit-gnome-authentication-agent-1:2166): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[MarcRandolph (mrand)]

Low, since you could just not use bookmarks.

[Gavin Hurlbut (gjhurlbu)]

One thing I don't see in the reports: How much memory and swap does this system have?

[Thomas Mashos (tgm4883)]

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream has moved on to a new version and believes this to be fixed. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.