mythfilldatabase crashed with SIGSEGV in QMutex::lock()

[laga+mythtv@…]

Hi,

this bug was forwarded from ​https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/210246

The current Ubuntu packages are built from revision 16838 so this bug might have been fixed already. Apport claims that the backtrace failed, but the resulting file is probably still useful.

When creating the ticket in Launchpad, the user suggested it could be related to database connection problems.

StacktraceTop:?? ()
QMutex::lock (this=0x8158e34) at tools/qmutex_unix.cpp:467
MythContext::ClearSettingsCache (this=0x8158ab0, myKey=@0xb48f00e8, newVal=@0xb48f00e4)
MythContext::readyRead (this=0x8158ab0, sock=0x817a090) at mythcontext.cpp:3333
readyReadThread_iffound (sock=0x817a090) at mythsocket.cpp:743

[laga+mythtv@…]

I should probably point out that we've got quite a few segfaults for mythfilldatabase in QMutex::lock(). See this page: ​https://bugs.launchpad.net/ubuntu/+source/mythtv?field.searchtext=mythfilldatabase+AND+QMutex%3A%3Alock()&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=

[stuartm]

Re-open with fresh backtraces if this still occurs in trunk or 0.22 upon it's release.