Mailing List Archive: MythTV: Users

mythbackend still eats memory: the current status

1 2 3 4 5 6 7

View All

Index | Next | Previous | View Threaded

udovdh at xs4all

Jan 4, 2009, 3:26 AM

Post #1 of 155 (4650 views)
Permalink

mythbackend still eats memory: the current status

Hello,

As you know MythTV, at least the backend, leaks resources.
Currently I am using svn 19412 of the 'fixes' branch.
Build Date: Sun 21 Dec 2008 03:57:00 PM CET
Install Date: Wed 24 Dec 2008 04:52:24 PM CET

Besides a few 'normal' schedules I run 3 `power searches` with queries like:
channel.callsign = "NL1" AND program.starttime < DATE_ADD( NOW( ) ,
INTERVAL 10 HOUR )
This is to record channels NL1, NL2, and NL3 24/7 off one multiplex and
to limit the amount of CPU the scheduler wastes on scheduling.

There is 1 minute preroll and postroll on every program, so I have 7
virtual tuners configured to avoid running out of tuners.
Of course I have 1 real tuner: a DVB-T card in my VIA EN-12000, which
has 1G of RAM and 1TB of disk.

The box just records, does not much else besides running Fedora 10.
I restarted the backend on 27th of december and since then gathered
these stats:

%CPU %MEM VSZ RSS TTY STAT START TIME
9.5 11.5 444464 112264 ? Ssl Dec27 93:15
9.6 12.3 450640 119536 ? Ssl Dec27 233:03
10.0 13.1 459412 127400 ? Ssl Dec27 385:30
10.1 14.2 470656 137924 ? Ssl Dec27 535:29
10.0 15.1 479536 146984 ? Ssl 2008 680:09
9.9 15.7 486244 153016 ? Ssl 2008 815:54
10.0 16.8 497588 163676 ? Ssl 2008 963:25
10.0 17.6 505328 171696 ? Ssl 2008 1108:20

As you can see the virtual size and resident size grow.
And keep growing all the time. (yes, they are)
It's *not just* caused by using EIT or because of the multirec feature.
(multirec is in 'fixes' and thus considered stable)
The issues was also there before I had EIT working.

Running valgrind to find the causes of the presumed leaks is not an
option due to the lack of CPU in this machine.

From what I read on this list other people also see similar behaviour
of the backend (continuously growing memory size).
It's dealt with by restarting the backend every now and then or maybe by
upgrading to another svn which forces a restart anyhow.

What can we do to fix most of the common leaks and make MythTV run more
stable this way?

Think of some test-suites to find the most obvious leaks?

Please post your ideas, maybe we can work something out in 2009!

Kind regards,
Udo

PS: w.r.t. CPU: where is that plug-in compatibility that VIA advertised
for the nano CPU? I want an EN-like board with PCI (not PCIe!) and a
faster nano CPU.
Same for LT/EK: no PCIe but PCI *with* nano CPU, please.

PS2: Is there a way to run a virtual environment with virtual tuners and
virtual signals for MythTV's virtual tuners? (my other box can do
VirtualBox etc)
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

robert.mcnamara at gmail

Jan 4, 2009, 10:08 AM

Post #2 of 155 (4522 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

Udo,

I'm fairly certain the last time this thread appeared the response was
the same as it will be now-- "help us help you." You are willing to
complain repeatedly about it on the list, but not even willing to
*try* to take the steps necessary to solve it. When you say "what can
*we*" do to solve the problem, you appear to mean, "when do *you* plan
to fix it for me." You've already been told what to do to provide
meaningful debug information. Remove any and all patches from your
system, and run valgrind. If you aren't able to provide information
that conclusively shows what the problem is, there's not a *single
person* who is going to waste time and effort chasing down phantom
causes for your problem.

You outright *refuse* to even *try* to run valgrind, but the point is
this. You run it, or you won't get any help on this matter. It's as
simple as that. Please don't turn this into a long, useless, drawn
out thread like the last one, as I'm fairly certain I'm giving an
accurate description of the thoughts of the people capable of helping
you with this. Everyone working on myth is a volunteer, and they/we
all work on the parts that interest us and make it fun. It is *not*
fun to hear complaints from someone unwilling to take the specific
(and ONLY) acceptable steps towards solving his problem. You *must*
meet people halfway, and that means removing your patches and running
valgrind. One last time: there *are* no other acceptable
troubleshooting steps that will get you response from people capable
of helping you.

Robert
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

greg at phaze

Jan 4, 2009, 10:39 AM

Post #3 of 155 (4513 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

> Running valgrind to find the causes of the presumed leaks is not an
> option due to the lack of CPU in this machine.
[SNIP]
> What can we do to fix most of the common leaks and make MythTV run more
> stable this way?
[SNIP]
> PS2: Is there a way to run a virtual environment with virtual tuners and
> virtual signals for MythTV's virtual tuners? (my other box can do
> VirtualBox etc)

If you have another box with a bigger CPU capable of running your
virtual then why not temporarily move your tuners/drives from the
slow machine to that one. Use valgrind on a clean unpatched build
and let it run a couple days to get the logs. Or is that too much trouble?

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

udovdh at xs4all

Jan 5, 2009, 7:27 AM

Post #4 of 155 (4483 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

Greg Estabrooks wrote:
> [SNIP]
>> PS2: Is there a way to run a virtual environment with virtual tuners and
>> virtual signals for MythTV's virtual tuners? (my other box can do
>> VirtualBox etc)
>
> If you have another box with a bigger CPU capable of running your
> virtual then why not temporarily move your tuners/drives from the
> slow machine to that one. Use valgrind on a clean unpatched build
> and let it run a couple days to get the logs. Or is that too much trouble?

I don't want to disrupt the current setup.
Not much trouble physically, but causing other dependencies w.r.t.
emulating the same environment as on the EN12000 perhaps?

Udo
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

udovdh at xs4all

Jan 5, 2009, 7:36 AM

Post #5 of 155 (4483 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

Robert McNamara wrote:
> You outright *refuse* to even *try* to run valgrind, but the point is

I *DID* run valgrind and it didn't work as intended. I posted about this
on the list so keeping up that I refuse is untrue
mythbackend ran in an unusual way without making recordings when
valgrind was active. so the sofwtare didn't perform as normal so
valgrind couldn't detect anything.

> this. You run it, or you won't get any help on this matter.

I posted a constructive message with details about the situation,
explanation about why I can't do much on the EN12000 (!) and you just
hammer that into the ground with a false statement.

It's as
> simple as that.

You made it just a bit more complicated by telling inaccuracies.

Please don't turn this into a long, useless, drawn
> out thread like the last one,

Your email could be made more to the point as a start.

> as I'm fairly certain I'm giving an
> accurate description of the thoughts of the people capable of helping
> you with this.

They voted you in for this?
They read my posting and the older postings as well as you did?

Everyone working on myth is a volunteer, and they/we
> all work on the parts that interest us and make it fun. It is *not*

I am not complaining, read my posting.

> fun to hear complaints from someone unwilling to take the specific
> (and ONLY) acceptable steps towards solving his problem.

Read my posting.

You *must*
> meet people halfway,

Read my posting.
I posted some constructive ideas.
Didn't you notice that?

and that means removing your patches and running
> valgrind.

My patches? 1 simple change for the amount of tuners?
Of which nobody said anything.

One last time: there *are* no other acceptable
> troubleshooting steps that will get you response from people capable
> of helping you.

Read my posting.
I posted some constructive ideas.
Didn't you notice that?

It's not just MY problem. It's the general situation with MythTV, didn't
you get that?
It leaks. A little and more for some.
I want to help to cure that.
I posted some constructive ideas.
Didn't you notice that?

And I am causing long threads?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

udovdh at xs4all

Jan 5, 2009, 8:18 AM

Post #6 of 155 (4492 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

Udo van den Heuvel wrote:
> Robert McNamara wrote:
>> You outright *refuse* to even *try* to run valgrind, but the point is
>
> I *DID* run valgrind and it didn't work as intended. I posted about this
> on the list so keeping up that I refuse is untrue
> mythbackend ran in an unusual way without making recordings when
> valgrind was active. so the sofwtare didn't perform as normal so
> valgrind couldn't detect anything.

http://www.gossamer-threads.com/lists/mythtv/users/338725?search_string=valgrind;#338725

You don't have to read it, just accept that I tried and that it didn't work.
Now I am trying to find other ways to be constructive.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

steve.p.daniels at googlemail

Jan 7, 2009, 1:02 AM

Post #7 of 155 (4443 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

2009/1/5 Udo van den Heuvel <udovdh [at] xs4all>
>
> Greg Estabrooks wrote:
> > [SNIP]
> >> PS2: Is there a way to run a virtual environment with virtual tuners and
> >> virtual signals for MythTV's virtual tuners? (my other box can do
> >> VirtualBox etc)
> >
> > If you have another box with a bigger CPU capable of running your
> > virtual then why not temporarily move your tuners/drives from the
> > slow machine to that one. Use valgrind on a clean unpatched build
> > and let it run a couple days to get the logs. Or is that too much trouble?
>
> I don't want to disrupt the current setup.
> Not much trouble physically, but causing other dependencies w.r.t.
> emulating the same environment as on the EN12000 perhaps?

That's all right, since it's a general problem (which you stated in a
later post) you won't need to emulate the EN12000 environment, plus
you've already said that valgrind didn't work on the EN12000 - Have
you tried a different distro/fresh install to eliminate a
configuration quirk of your current system that is causing valgrind
not to work?

So now all you need to do mirror your MythTV configuration off the
EN12000 onto your other box then setup valgrind and watch for the
leaks :-) That seems to be the most expedient thing to do - or just
wait patiently for someone else to do just that instead of you.

Good luck :-)

>
> Udo

Steve Daniels
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

udovdh at xs4all

Jan 7, 2009, 8:09 AM

Post #8 of 155 (4438 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

Steve Daniels wrote:
>> Not much trouble physically, but causing other dependencies w.r.t.
>> emulating the same environment as on the EN12000 perhaps?
>
> That's all right, since it's a general problem (which you stated in a
> later post) you won't need to emulate the EN12000 environment, plus
> you've already said that valgrind didn't work on the EN12000 - Have
> you tried a different distro/fresh install to eliminate a
> configuration quirk of your current system that is causing valgrind
> not to work?

Valgrind ran bu the load of mythbackend *AND** valgrind was too much.
I wrote about that.
How can a distro help here?
Or does valgrind need much optimisation when building it?

> So now all you need to do mirror your MythTV configuration off the
> EN12000 onto your other box then setup valgrind and watch for the
> leaks :-) That seems to be the most expedient thing to do - or just
> wait patiently for someone else to do just that instead of you.

OK, so how do I do that without moving the DVB card?

Udo
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

greg at phaze

Jan 7, 2009, 8:23 AM

Post #9 of 155 (4424 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

> I don't want to disrupt the current setup.
> Not much trouble physically, but causing other dependencies w.r.t.
> emulating the same environment as on the EN12000 perhaps?

A supposed mythtv Memory leak is not likely related to
your motherboard or CPU :) Just move the drives and tuners
and build from clean source.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

steve.p.daniels at googlemail

Jan 7, 2009, 8:26 AM

Post #10 of 155 (4431 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

2009/1/7 Udo van den Heuvel <udovdh [at] xs4all>:
> Steve Daniels wrote:
>>> Not much trouble physically, but causing other dependencies w.r.t.
>>> emulating the same environment as on the EN12000 perhaps?
>>
>> That's all right, since it's a general problem (which you stated in a
>> later post) you won't need to emulate the EN12000 environment, plus
>> you've already said that valgrind didn't work on the EN12000 - Have
>> you tried a different distro/fresh install to eliminate a
>> configuration quirk of your current system that is causing valgrind
>> not to work?
>
> Valgrind ran bu the load of mythbackend *AND** valgrind was too much.
> I wrote about that.
> How can a distro help here?
> Or does valgrind need much optimisation when building it?

I remember now, sorry about that, a lighter weight setup might help
but it'd likely take too long to get it running. Consider moving the
entire setup to the more powerful machine and using the EN12000 as
your desktop for a short while?

>
>> So now all you need to do mirror your MythTV configuration off the
>> EN12000 onto your other box then setup valgrind and watch for the
>> leaks :-) That seems to be the most expedient thing to do - or just
>> wait patiently for someone else to do just that instead of you.
>
> OK, so how do I do that without moving the DVB card?

Same way anyone else would, buy another one :-) Or see if it
experiences the same problems with a a Network IP Recorder (You can
simulate a source with VLC)

>
> Udo

Both of these suggestions require investment of either or both of two
resources, your time and/or money. (Or someone elses, but no one else
seems driven enough by the problems so it seems it's up to you :-)

Steve Daniels
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

udovdh at xs4all

Jan 7, 2009, 8:44 AM

Post #11 of 155 (4431 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

Steve Daniels wrote:
> 2009/1/7 Udo van den Heuvel <udovdh [at] xs4all>:
>> Steve Daniels wrote:
>>> you tried a different distro/fresh install to eliminate a
>>> configuration quirk of your current system that is causing valgrind
>>> not to work?
>> Valgrind ran bu the load of mythbackend *AND** valgrind was too much.
>> I wrote about that.
>> How can a distro help here?
>> Or does valgrind need much optimisation when building it?
>
> I remember now, sorry about that, a lighter weight setup might help
> but it'd likely take too long to get it running. Consider moving the
> entire setup to the more powerful machine and using the EN12000 as
> your desktop for a short while?

Not so possible.
I didn't build a Phenom setup with 4G and 4-drive raid5 to waste watts
while my desktop crawls?

>> OK, so how do I do that without moving the DVB card?
>
> Same way anyone else would, buy another one :-)

80 euro? I spent less on the multirec feature.

> Both of these suggestions require investment of either or both of two
> resources, your time and/or money. (Or someone elses, but no one else
> seems driven enough by the problems so it seems it's up to you :-)

Hmmm. If only I could get a virtual tuner (or virtual signal) I could
virtualbox the whole thing.

Udo
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

udovdh at xs4all

Jan 7, 2009, 8:45 AM

Post #12 of 155 (4424 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

Greg Estabrooks wrote:
>> I don't want to disrupt the current setup.
>> Not much trouble physically, but causing other dependencies w.r.t.
>> emulating the same environment as on the EN12000 perhaps?
>
>
> A supposed mythtv Memory leak is not likely related to
> your motherboard or CPU :) Just move the drives and tuners
> and build from clean source.

?
And then suffer the issues that a good backup requires deleting the
tuner setup before mythTV can continue?
No thanks.
I can run a virtual system on the desktop.
Not much else, practically.

Udo
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

robert.mcnamara at gmail

Jan 7, 2009, 8:48 AM

Post #13 of 155 (4434 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

On Wed, Jan 7, 2009 at 8:45 AM, Udo van den Heuvel <udovdh [at] xs4all> wrote:
> Greg Estabrooks wrote:
>>> I don't want to disrupt the current setup.
>>> Not much trouble physically, but causing other dependencies w.r.t.
>>> emulating the same environment as on the EN12000 perhaps?
>>
>>
>> A supposed mythtv Memory leak is not likely related to
>> your motherboard or CPU :) Just move the drives and tuners
>> and build from clean source.
>
> ?
> And then suffer the issues that a good backup requires deleting the
> tuner setup before mythTV can continue?
> No thanks.
> I can run a virtual system on the desktop.
> Not much else, practically.
>
> Udo
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

This is deja vu all over again. It goes/went like this:

1) Valid suggestion for how to provide debug information.
2) Refusal.
3) GOTO 1.

Time for some banhammerage, I think.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

udovdh at xs4all

Jan 7, 2009, 8:53 AM

Post #14 of 155 (4429 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

Robert McNamara wrote:
>> I can run a virtual system on the desktop.
>> Not much else, practically.
>>
> This is deja vu all over again. It goes/went like this:

And you just waste bandwidth by pointing out your supposed `solution`
(the pestering of certain posters).
It appears you can't accept that other people live other lives than you,
have other opportunities and choices than you have.

> 1) Valid suggestion for how to provide debug information.

Valid but usable?

> 2) Refusal.

black or white. Nothing else of course.

> 3) GOTO 1.

You do so.

Udo
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

greg at phaze

Jan 7, 2009, 9:01 AM

Post #15 of 155 (4427 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

> > A supposed mythtv Memory leak is not likely related to
> > your motherboard or CPU :) Just move the drives and tuners
> > and build from clean source.
>
> ?
> And then suffer the issues that a good backup requires deleting the
> tuner setup before mythTV can continue?

What? Why would you need to delete the tuners?

You are just moving the drives and the cards. WORST case the cards
might be detected in a different order and that is highly unlikely.

Same hardrives, same distro, same database, same configuration.

Of course do a mysql dump for safety but other than that it should
be a fairly simple operation.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

steve.p.daniels at googlemail

Jan 7, 2009, 9:10 AM

Post #16 of 155 (4419 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

2009/1/7 Udo van den Heuvel <udovdh [at] xs4all>:
> Steve Daniels wrote:
>> 2009/1/7 Udo van den Heuvel <udovdh [at] xs4all>:
>>> Steve Daniels wrote:
>>>> you tried a different distro/fresh install to eliminate a
>>>> configuration quirk of your current system that is causing valgrind
>>>> not to work?
>>> Valgrind ran bu the load of mythbackend *AND** valgrind was too much.
>>> I wrote about that.
>>> How can a distro help here?
>>> Or does valgrind need much optimisation when building it?
>>
>> I remember now, sorry about that, a lighter weight setup might help
>> but it'd likely take too long to get it running. Consider moving the
>> entire setup to the more powerful machine and using the EN12000 as
>> your desktop for a short while?
>
> Not so possible.
> I didn't build a Phenom setup with 4G and 4-drive raid5 to waste watts
> while my desktop crawls?

Ok, this is where I fall off my seat and stop being reasonable. You've
got the money to do that, but don't want to "waste" your own time and
money debugging you current memory leak issues but you want others to
spend their own time and money doing it. That is simply disrespectful
and insulting to anyone.

>
>>> OK, so how do I do that without moving the DVB card?
>>
>> Same way anyone else would, buy another one :-)
>
> 80 euro? I spent less on the multirec feature.
>
>> Both of these suggestions require investment of either or both of two
>> resources, your time and/or money. (Or someone elses, but no one else
>> seems driven enough by the problems so it seems it's up to you :-)
>
> Hmmm. If only I could get a virtual tuner (or virtual signal) I could
> virtualbox the whole thing.

I've just told you that you could try and see if the memory leak is
still present with the IPTV recorder. If your willing to buy another
cheap DVB tuner there are virtualisation solutions that allow you to
pass-through the PCI and/or USB devices to the guest OS.

Good luck.

>
> Udo

Good bye.

Steve Daniels
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

ryan.goat at gmail

Jan 7, 2009, 9:12 AM

Post #17 of 155 (4429 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

On Wed, Jan 7, 2009 at 11:53 AM, Udo van den Heuvel <udovdh [at] xs4all> wrote:
> Robert McNamara wrote:
>>> I can run a virtual system on the desktop.
>>> Not much else, practically.
>>>
>> This is deja vu all over again. It goes/went like this:
>
> And you just waste bandwidth by pointing out your supposed `solution`
> (the pestering of certain posters).
> It appears you can't accept that other people live other lives than you,
> have other opportunities and choices than you have.
>
>> 1) Valid suggestion for how to provide debug information.
>
> Valid but usable?
>
>> 2) Refusal.
>
> black or white. Nothing else of course.
>
>> 3) GOTO 1.
>
> You do so.
>
> Udo
>

Udo,

You are being very obtuse. It is clear a solution to your problem
will involve you doing some work or spending some money.

-Ryan

--
_____________
Ryan Patterson
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

belcampo at zonnet

Jan 7, 2009, 9:40 AM

Post #18 of 155 (4437 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

Udo van den Heuvel wrote:
> Steve Daniels wrote:
>> 2009/1/7 Udo van den Heuvel <udovdh [at] xs4all>:
>>> Steve Daniels wrote:
>>>> you tried a different distro/fresh install to eliminate a
>>>> configuration quirk of your current system that is causing valgrind
>>>> not to work?
>>> Valgrind ran bu the load of mythbackend *AND** valgrind was too much.
>>> I wrote about that.
>>> How can a distro help here?
>>> Or does valgrind need much optimisation when building it?
>> I remember now, sorry about that, a lighter weight setup might help
>> but it'd likely take too long to get it running. Consider moving the
>> entire setup to the more powerful machine and using the EN12000 as
>> your desktop for a short while?
>
> Not so possible.
> I didn't build a Phenom setup with 4G and 4-drive raid5 to waste watts
> while my desktop crawls?
So you're saying the problem is that small that a few watts for a few
days is too much.
>
>>> OK, so how do I do that without moving the DVB card?
>> Same way anyone else would, buy another one :-)
>
> 80 euro? I spent less on the multirec feature.
>
>> Both of these suggestions require investment of either or both of two
>> resources, your time and/or money. (Or someone elses, but no one else
>> seems driven enough by the problems so it seems it's up to you :-)
>
> Hmmm. If only I could get a virtual tuner (or virtual signal) I could
> virtualbox the whole thing.
>
> Udo
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

udovdh at xs4all

Jan 7, 2009, 9:41 AM

Post #19 of 155 (4432 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

ryan patterson wrote:
> You are being very obtuse. It is clear a solution to your problem
> will involve you doing some work or spending some money.

Pffff.
You picture everything the wrong way.
As If I don't want to do anything.
That's a lie and you know it.
Why else would I start (again..) about the whole situation?
Why would I post some constructively meant questions/ideas at the bottom
of that status mail?

About spending money on hardware I don't need:

What if I spend it on a fee for a programmer?
(just forget about me paying for the multirec feature)

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

robert.mcnamara at gmail

Jan 7, 2009, 9:48 AM

Post #20 of 155 (4426 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

On Wed, Jan 7, 2009 at 9:41 AM, Udo van den Heuvel <udovdh [at] xs4all> wrote:
> ryan patterson wrote:
>> You are being very obtuse. It is clear a solution to your problem
>> will involve you doing some work or spending some money.
>
> Pffff.
> You picture everything the wrong way.
> As If I don't want to do anything.
> That's a lie and you know it.
> Why else would I start (again..) about the whole situation?
> Why would I post some constructively meant questions/ideas at the bottom
> of that status mail?
>

There's a saying here that insanity is doing the same thing over and
over again and expecting a different result. Sometimes the answers
aren't as we like, but they're the only answers out there. You can
move the tuners to another system and set up a similar use case, and
valgrind there, you can get valgrind working on your current setup.
That's *it*, Udo, there aren't going to be any more suggestions
forthcoming. They're the only answers out there.

> About spending money on hardware I don't need:
>
> What if I spend it on a fee for a programmer?
> (just forget about me paying for the multirec feature)
>
>

There is a *difference* between contributing to a bounty and
purchasing a feature. You are *not owed anything* for having
contributed to the bounty. The bounty paid for the work done to
acheive the feature, and not an ounce more. In fact, give how much it
was per hour of programming, it was probably a pretty insulting hourly
fee. That said, the Multirec bounty has NOTHING to do with this case.
Nobody owes you anything. As we also say here, "put up or shut up."

Robert

>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

udovdh at xs4all

Jan 7, 2009, 9:50 AM

Post #21 of 155 (4445 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

Steve Daniels wrote:
>> while my desktop crawls?
>
> Ok, this is where I fall off my seat and stop being reasonable.

You can, please go ahead.
Not everyone makes your choices.
I make mine in my way.
The setup I mentioned is a cheap one, built from simple components to
reduce power consumption.

> You've
> got the money to do that, but don't want to "waste" your own time

No! Didn't say that.
You put those words in my mouth.

> and
> money

Didn't say that.
You put those words in my mouth.

I just don't want to disrupt the recording.
I don't want to mess with the desktop (too much).
Both systems must be usable most of the time. That's what they are for.

debugging you current memory leak issues but you want others to
> spend their own time and money doing it. That is simply disrespectful
> and insulting to anyone.

You draw your overreacting conclusions in your time.
I just use my time in my way, especially if you all react so nicely to a
constructively meant status report.

> I've just told you that you could try and see if the memory leak is
> still present with the IPTV recorder.

Can give that a try this weekend.
I'll try to make virtualbox run with Fedora 10 i386 and install MytHTV
in there.
In the mean time I must get familiar with IPTV I guess.

Was the wording of my constructive status report off?
Why does everybody forget about me trying valgrind?
Why is everybody hostile?
Is it the crisi$ zeitgeist?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

robert.mcnamara at gmail

Jan 7, 2009, 9:54 AM

Post #22 of 155 (4436 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

>
> Was the wording of my constructive status report off?
> Why does everybody forget about me trying valgrind?
> Why is everybody hostile?
> Is it the crisi$ zeitgeist?
>

Although I wouldn't expect this level of introspection, it would be
reasonable to assume that if everyone is responding this way, that you
may be in the wrong. I don't know if it's language barriers, but you
are coming across as very intractable and not at all willing to do any
work to help. You may not know who has been responding to you, but
several of them have been myth devs. You have burned those bridges
and I know they are no longer interested in spending an ounce of
energy helping you with this.

I mean this in a friendly, helpful way: You need to re-evaluate the
way you are behaving.

Robert
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

gull at gull

Jan 7, 2009, 10:05 AM

Post #23 of 155 (4422 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

On Wed, January 7, 2009 9:41 am, Udo van den Heuvel wrote:
> What if I spend it on a fee for a programmer?
> (just forget about me paying for the multirec feature)

You could spend it on Windows Media Center. Then you wouldn't have to
deal with the developers here that you seem to dislike so much. You could
pester Microsoft about your problems instead.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

kkuphal at gmail

Jan 7, 2009, 10:12 AM

Post #24 of 155 (4423 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

On Wed, Jan 7, 2009 at 11:50 AM, Udo van den Heuvel <udovdh [at] xs4all>wrote:

>
> I just don't want to disrupt the recording.
> I don't want to mess with the desktop (too much).
> Both systems must be usable most of the time. That's what they are for.

If it isn't worth your effort to stop recording *television* or use your
desktop PC for a short period of time to valgrind on a more powerful
motherboard/CPU combo, then I don't think you're going to find much
sympathy/support from anyone else for whatever kind of time you're thinking
someone else should put in to try to diagnose this for you.

Kevin

udovdh at xs4all

Jan 9, 2009, 6:06 AM

Post #25 of 155 (4329 views)
Permalink

Re: mythbackend still eats memory: the current status [In reply to]

belcampo wrote:
>> I didn't build a Phenom setup with 4G and 4-drive raid5 to waste watts
>> while my desktop crawls?
> So you're saying the problem is that small that a few watts for a few
> days is too much.

Again someone putting words where they aren't.
Why should I suddenly invest cash when there's a (possible) software
solution?
I just don't want to mess with the current setups of bpth my desktop and
the MythTV box.
I can assist with a virtual MythTV system on the desktop, running inside
virtualbox, though.

Udo
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

1 2 3 4 5 6 7

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads