mythcommflag assert failure: *** glibc detected *** /usr/bin/mythcommflag: invalid fastbin entry (free): 0x00007f22ec0164b0 ***

Bug #1186626 reported by D. Hugh Redelmeier
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Expired
Undecided
Unassigned

Bug Description

MythTV has been popping up a few crash messages recently. This is the first that would allow me to report: earlier crashes were while there were updated packages that I hadn't installed.

according to code.mythtv.org/trac/ticket/10201 some other people are experiencing the same symptom. That ticket is locked with because they beleive "glibc bug, not mythtv bug". Of the two new reports in the last few days, both are on Ubuntu systems whereas earlier ones were on Fedora (I haven't checked carefully).

On comment on that ticket is that https://bugzilla.redhat.com/show_bug.cgi?id=593396 includes a glibc patch that fixes this symptom.

Summary: this might be a glibc bug with a known fix.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-backend 2:0.26.0+fixes.20130530.bfd2408-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.26]
ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
Uname: Linux 3.2.0-38-generic x86_64
NonfreeKernelModules: nvidia
.var.log.mythtv.mtd.log:
 mtd started at Sat Jan 8 00:13:43 2011
 mtd is running on a host called redblack
 00:13:43: Waiting for connections/jobs
 00:13:43: mtd is listening on port 2442
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythlcdserver.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythmetadatalookup.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythtranscode.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/bin/mythcommflag: invalid fastbin entry (free): 0x00007f22ec0164b0 ***
CrashDB: mythbuntu
Date: Sat Jun 1 04:01:15 2013
ExecutablePath: /usr/bin/mythcommflag
Installed_mythtv_dbg: 2:0.26.0+fixes.20130530.bfd2408-0ubuntu0mythbuntu1
MarkForUpload: True
ProcCmdline: /usr/bin/mythcommflag -j 4586 --noprogress --verbose general --loglevel info --quiet --syslog local7
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
Signal: 6
SourcePackage: mythtv
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f23200c5008 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=3, str=0x7f23200c192b "invalid fastbin entry (free)", ptr=<optimized out>) at malloc.c:5018
 tzset_internal (explicit=<optimized out>, always=<optimized out>) at tzset.c:435
 __tzset () at tzset.c:590
 QTime::currentTime () at tools/qdatetime.cpp:3116
Title: mythcommflag assert failure: *** glibc detected *** /usr/bin/mythcommflag: invalid fastbin entry (free): 0x00007f22ec0164b0 ***
UpgradeStatus: Upgraded to precise on 2013-03-01 (92 days ago)
UserGroups: audio cdrom dialout video

Revision history for this message
D. Hugh Redelmeier (hugh-mimosa) wrote :
Revision history for this message
D. Hugh Redelmeier (hugh-mimosa) wrote :

The trac ticket I reported points at a glibc patch from Red Hat. My Ubuntu 12.04 glibc already has that patch, so it cannot be the fix.

information type: Private → Public
Revision history for this message
Thomas Mashos (tgm4883) wrote :

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.

Changed in mythbuntu:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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