Mythbuntu

mythfilldatabase crashed with SIGSEGV in calloc()

Bug #1072196 reported by Vivek Mittal on 2012-10-27

74

This bug affects 16 people

Affects		Status	Importance	Assigned to	Milestone
	Mythbuntu	Expired	Undecided	Unassigned

Bug Description

mythfilldatabase has been crashing for me ever since I upgraded to the latest version of Ubuntu and MythTV. It does not happen at every instance, but does happen atleast once a day. I have not noticed any drawbacks in my system due to this - my TV schedules are still populated, so have ignored it till now.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-backend 2:0.26.0+fixes.20121026.0de21aa-0ubuntu0mythbuntu2 [origin: LP-PPA-mythbuntu-0.26]
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
.var.log.mythtv.mtd.log:
mtd started at Mon Nov 1 21:02:22 2010
mtd is running on a host called duper
21:02:22: Waiting for connections/jobs
21:02:22: mtd is listening on port 2442
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythfilldatabase.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
CrashCounter: 1
CrashDB: mythbuntu
Date: Sun Oct 28 04:46:04 2012
ExecutablePath: /usr/bin/mythfilldatabase
InstallationMedia: Mythbuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythfilldatabase
ProcEnviron:
PATH=(custom, no user)
LANG=en_AU.UTF-8
SHELL=/bin/sh
SegvAnalysis:
Segfault happened at: 0x7f2597133df2: mov 0x8(%rbx),%rdx
PC (0x7f2597133df2) ok
source "0x8(%rbx)" (0x100000009) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /lib/x86_64-linux-gnu/libc.so.6
calloc () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /usr/lib/nvidia-current/libGL.so.1
?? () from /usr/lib/nvidia-current/libGL.so.1
Title: mythfilldatabase crashed with SIGSEGV in calloc()
UpgradeStatus: Upgraded to precise on 2012-09-01 (56 days ago)
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video

Tags:

Revision history for this message

Vivek Mittal (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1ohg85w3jabxlrqbgszpjpwcmvkbcvq9spp6z3w5j1m33k06tlsfszeuscyt241-launchpad) wrote on 2012-10-27:

#1

.var.log.mythtv.jamu.log.txt Edit (1.4 MiB, text/plain; charset="utf-8")
.var.log.mythtv.mythbackend.log.txt Edit (1.5 MiB, text/plain; charset="utf-8")
.var.log.mythtv.mythcommflag.log.txt Edit (358.7 KiB, text/plain; charset="utf-8")
.var.log.mythtv.mythfrontend.log.txt Edit (2.2 MiB, text/plain; charset="utf-8")
.var.log.mythtv.mythlcdserver.log.txt Edit (233.7 KiB, text/plain; charset="utf-8")
.var.log.mythtv.mythmetadatalookup.log.txt Edit (257.8 KiB, text/plain; charset="utf-8")
.var.log.mythtv.mythpreviewgen.log.txt Edit (531.9 KiB, text/plain; charset="utf-8")
.var.log.mythtv.mythtranscode.log.txt Edit (15.2 KiB, text/plain; charset="utf-8")
.var.log.mythtv.mythtv.setup.log.txt Edit (104.7 KiB, text/plain; charset="utf-8")
CoreDump.gz Edit (2.7 MiB, application/x-gzip)
Dependencies.txt Edit (9.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (651 bytes, text/plain; charset="utf-8")
MythTVDirectoryPermissions.txt Edit (747 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (54.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (828 bytes, text/plain; charset="utf-8")
Registers.txt Edit (785 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.8 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (11.2 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (32.7 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

paul summers (paulsum) wrote on 2012-10-31:

#2

i have noticed that the commerical detection, crashes "failed with exit status 140"

but it seems that when program "recorded via antenna (ATSC)" has any cubing or a bad recording because the reception was bad it crashes.

i am using an amd c60, i have not tested with an intel i3... (i had one long story)... so possibly it is a amd processor problem.
(rumours that intel libraries are not "kind" to amd processors... outlandish... but who knows

Revision history for this message

John M (e-launchpad-e-wuuza) wrote on 2012-11-18:

#3

This seems similar to my issue (1077778). After upgrading to 12.04 I got a lot of crashes in mythshutdown and mythpreviewgen. What motherboard do you have? Mine's a GIGABYTE GA-MA785GM-US2H, and I'm using a Zotac GT-220. Since the problems started immediately after upgrading I wonder if there's some sort of hardware incompatibility that was suddenly exposed...?

Revision history for this message

Vivek Mittal (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1ohg85w3jabxlrqbgszpjpwcmvkbcvq9spp6z3w5j1m33k06tlsfszeuscyt241-launchpad) wrote on 2012-11-19:

#4

I've got a Gigabyte GA-MA69GM-S2H motherboard and using onboard graphics.

Revision history for this message

paul summers (paulsum) wrote on 2012-12-13:

#5

i justignore it... it just generates the picture... great thing is mythcommflag has not crashed also!..

I have reinstall linux, (lucky that i have a separate /home partition.... (and found an easy/working database restore (from scratch) method... (because the mythback utility did not detect the back-up that was generated automatically (even when i pointed the program at the file... lucky that i used the "gunzip [...].sql.gz... transfer into mysql fix...

in any case, and sorry if this is repetitive!... MAKE SURE YOU HAVE A BACKUP THAT WORKS!... test it or find out where they are stored!... it is disaster it you have 1.5TB of tv Shows and no database... yes you can watch them with VLC... but you did not want to start over!.... CHECK YOUR DATABASE BACKUP LOCATION... for A recent backup...

TL;DR... this bug is just annoying... that is all....

Revision history for this message

paul summers (paulsum) wrote on 2012-12-20:

#6

i mfiled this bug here because the bug matches the title of the others... does not really affect me because i don't see any damage

Revision history for this message

keepitsimpleengr (keepitsimpleengineer) wrote on 2012-12-23:

#7

it happened again

Revision history for this message

Peter D. (0123peter) wrote on 2013-07-27:

#8

Seems to be a harmless, but mildly annoying, recurrent problem.

Revision history for this message

Peter D. (0123peter) wrote on 2013-08-18:

#9

New hard drive, power supply, mobo, cpu & mem. Fresh install, upgraded to 0.26, ran backend setup, closed backend setup, clicked "yes" for a couple of things -- crashed.

Revision history for this message

Thomas Mashos (tgm4883) wrote on 2015-01-10:

#10

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

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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