mythfilldatabase crashed with SIGSEGV in MythDB::ClearSettingsCache()

[Duey]

Binary package hint: mythtv

I keep getting this crash, and it would tell me to update packages first. I have updated packages and still getting this crash. I'm not sure what's causing it. I do have mythfilldatabase running in the morning (via cron) to make sure the listings for the day are up-to-date, but crashes don't really show up in the morning.

Description: Ubuntu 10.04.1 LTS
Release: 10.04

$ apt-cache policy mythtv
mythtv:
  Installed: 0.23.0+fixes24158-0ubuntu2
  Candidate: 0.23.0+fixes24158-0ubuntu2
  Version table:
 *** 0.23.0+fixes24158-0ubuntu2 0
        500 http://ca.archive.ubuntu.com/ubuntu/ lucid/multiverse Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: mythtv-backend 0.23.0+fixes24158-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
CrashCounter: 1
Date: Mon Oct 11 19:01:33 2010
ExecutablePath: /usr/bin/mythfilldatabase
Installed_mythplugins-dbg: 0.0
Installed_mythtv-dbg: 0.0
ProcCmdline: /usr/bin/mythfilldatabase
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x71e569 <_ZN6MythDB18ClearSettingsCacheERK7QString+21>: mov (%eax),%eax
 PC (0x0071e569) ok
 source "(%eax)" (0x24048944) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 MythDB::ClearSettingsCache(QString const&) ()
 MythContext::ClearSettingsCache(QString const&) ()
 MythContext::readyRead(MythSocket*) ()
 MythSocketThread::ReadyToBeRead(MythSocket*) ()
 MythSocketThread::run() () from /usr/lib/libmythdb-0.23.so.0
Title: mythfilldatabase crashed with SIGSEGV in MythDB::ClearSettingsCache()
UserGroups: audio cdrom dialout video

[Duey (dueydotnet)]

Hmmm. Crash counter = 1? Perhaps this is unrelated to the crashes I had before. I had updated packages yesterday.

Actually, according to Mythweb, it shows the status of "Last mythfilldatabase run started on 2010-10-11 19:01 and ended on 2010-10-11 19:01. Successful." If the crash data doesn't show anything obvious, it might have been a fluke. I'll report any more crashes as I catch them.

[Apport retracing service (apport)]

StacktraceTop:
 MythDB::ClearSettingsCache ()
 MythContext::ClearSettingsCache ()
 MythContext::readyRead () from /usr/lib/libmyth-0.23.so.0
 MythSocketThread::ReadyToBeRead ()
 MythSocketThread::run () from /usr/lib/libmythdb-0.23.so.0

[MarcRandolph (mrand)]

Howdy, and thank you for helping to improve MythTV by opening this ticket. Unfortunately, through no fault of your own, the attached stacktrace is not useful to the developers. Could you please update to the latest version of the debug packages by following the "basic backtrace" directions outlined here:

http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages

The above process should result in a new ticket being opened if you can reproduce the issue, so I'm going to close this ticket.