mythbackend crashed with SIGSEGV in free()

Bug #371782 reported by Richard Brooklyn on 2009-05-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Won't Fix
mythtv (Ubuntu)

Bug Description

Binary package hint: mythtv

Apport crash report appeared on screen and eventually sent me here to report the bug.

Mythtv usually crashes about once a day over here with random timing and reasons. It's so bad I have to set up a crontab to check if it's running every ten minutes and get it restarted here. This is the first time the system has actually picked up on it.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/mythbackend
Package: mythtv-backend 0.21.0+fixes16838-0ubuntu3.1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/mythbackend --daemon --logfile /var/log/mythtv/mythbackend.log --pidfile /var/run/mythtv/
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: mythtv
 free () from /lib/tls/i686/cmov/
 operator delete () from /usr/lib/
 operator delete[] () from /usr/lib/
 QStringData::~QStringData () from /usr/lib/
 QStringData::deleteSelf () from /usr/lib/
Title: mythbackend crashed with SIGSEGV in free()
Uname: Linux 2.6.24-23-generic i686
UserGroups: audio cdrom dialout video

Richard Brooklyn (rbrooklyn) wrote :

StacktraceTop:free () from /lib/tls/i686/cmov/
operator delete (ptr=0x9)
operator delete[] (ptr=0x11)
~QStringData (this=0x822c5b0) at tools/qstring.h:366
QStringData::deleteSelf (this=0x822c5b0)

Changed in mythtv (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Changed in mythtv:
status: Unknown → New
MarcRandolph (mrand) wrote :

Howdy, and thank you very much helping to improve Mythbuntu by taking the time to open this ticket.

 I am closing this ticket for a combination of reasons:

1. It is missing symbol information needed to help debug the issue
2. The version of QT string handling was totally re-written with QT4 for 0.22, so it is likely this is fixed
3. There are no other reports of this issue
4. This issue would need to be reproduced on 0.22 with a new stack trace since the mythtv developers are no longer working on 0.21 issues

If you can reproduce this on 0.22, please attach traces to a new ticket and we can try to forward this bug upstream to get the right eyes focused on it. We have builds of mythtv 0.22 available on a PPA to test. Please follow the directions at to enable them.

WARNING: If you think that you may want or need to revert back to 0.21 after testing, you will need to back up your database before upgrading. Once you upgrade, the only method to down-grade is to perform a database restore from your backup.

    Thanks again!

Changed in mythtv (Ubuntu):
status: New → Invalid
Changed in mythtv:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.