Hi,
I have upgraded to current Karmic since reporting this issue - obviously this
is not affecting 0.22.
I close this.
--
mythtv-backend crash: memory corruption
https://bugs.launchpad.net/bugs/267274
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Howdy, 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 the MythTV developers have turned their efforts to
the next version (0.22) and beyond and are no longer fixing bugs on
0.21.
The Mythbuntu
Howdy! This ticket is quite old and the mythtv developers upstream have
stopped focusing on 0.21 based reports in preparation for a 0.22 release
later this year. Can you please try to see if this bug is reproducible
on 0.22? If it is, we can try to forward this bug upstream to get the
right eyes
I've had three crashes of mythtbackend in the last month.
$ grep -A 1 -B 3 -Hn Backtrace /var/log/mythtv/mythbackend.log*
/var/log/mythtv/mythbackend.log-34128-2009-07-30 15:00:01.013 Finished
recording Guiding Light: channel 1021
/var/log/mythtv/mythbackend.log-34129-2009-07-30 15:00:01.013
for me it lasts many hours, but less than two days. so I have a cron to
restart it at 5 am
every day... it seems to be mostly good enough now...
--
mythtv-backend crash: memory corruption
https://bugs.launchpad.net/bugs/267274
You received this bug notification because you are a member of
Plus one here.. Totally strange
--
mythtv-backend crash: memory corruption
https://bugs.launchpad.net/bugs/267274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm getting segfaults on myth-backend every few hours. How do I start to
debug this?
What info do I need to collect?
--
mythtv-backend crash: memory corruption
https://bugs.launchpad.net/bugs/267274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm running KDE 4, and plasma seems to have a memory leak. It looks like it
takes more and more memory, and then, I am guessing, a malloc fails in
mythtv and it dies.
On Fri, Dec 19, 2008 at 1:44 AM, Jason Diesel jason.die...@gmail.comwrote:
I am just starting to get the same.
$cat
I am just starting to get the same.
$cat /var/log/messages | grep myth
Dec 15 19:38:56 pacific kernel: [148418.947708] mythfilldatabas[14805] general
protection ip:96bcb3a sp:b545080c error:0
Dec 17 20:06:54 pacific kernel: [70332.983297] mythbackend[6975]: segfault at
730071 ip b5cb3c92 sp
mee too, it keeps crashing once or twice a day...
2008-11-20 20:34:40.902 AutoExpire: CalcParams(): Max required Free Space: 3.0
GB w/freq: 15 min
2008-11-20 20:34:40.986 Expiring 1044 MBytes for 1034 @ Wed Oct 29 19:00:00
2008 = Chaotic. Too many episodes, we only want to keep 9.
2008-11-20
Today backend has crashed with following in syslog:
[56280.301003] mythbackend[6502]: segfault at 6f004e0c ip b5ce9c32 sp b103d0c4
error 4 in libc-2.8.90.so[b5c7a000+158000]
Crash file was created and it is attached. There was nothing in
/var/log/mythtv/mythbackend.log this time
** Attachment
** Attachment added: mythbackend.log
http://launchpadlibrarian.net/17353068/mythbackend.log
--
mythtv-backend crash: memory corruption
https://bugs.launchpad.net/bugs/267274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
12 matches
Mail list logo
