Page 1 of 1

Large RAM footprint

Posted: Sun Nov 22, 2009 10:22 am
by soulraven
can not reduce the memory consumption of ProgDVB? now stands at 160MB. Why eat so much?
http://img694.imageshack.us/i/bug3i.jpg/

Re: Large RAM footprint

Posted: Sun Nov 29, 2009 12:21 am
by John
soulraven wrote:can not reduce the memory consumption of ProgDVB? now stands at 160MB. Why eat so much?
http://img694.imageshack.us/i/bug3i.jpg/
maybe cause doesnt use MultiThreading or not well coded
try to disable skin.

.

Posted: Sun Nov 29, 2009 8:17 am
by Prog
Yes, 150-160 mbyte it is typically for ProgDVB. Many processes, many buffers, .net interface...
You can try disable skin, disable EPG and tetelext parsing, disable timeshift (or use on HDD).

Posted: Sun Nov 29, 2009 11:56 pm
by Juergen
Well, look at EXPLORER.EXE, on the same picture.
Just a stupid file manager.
Fat and lazy...
'Cause it's original MS stuff.
.NET also is, and ProgDVB uses it.

Anyway, on modern computers, you should have more than enough of RAM inside. Else perhaps spend another tenner...
Older machines could also benefit from additional RAM, as long as the type needed still is available.
Or check out older versions of ProgDVB, IF they already support your tuner.

Re: .

Posted: Thu Dec 03, 2009 10:58 am
by hosavag
Prog wrote:Yes, 150-160 mbyte it is typically for ProgDVB. Many processes, many buffers, .net interface...
You can try disable skin, disable EPG and tetelext parsing, disable timeshift (or use on HDD).
I had the same strange thing with v 23.1 but with a lot more memory usage, after some hours of work the ProgDVB has allocated ~ 1GB of memory, is it normal ? the timeshift is disabled. restarting the ProgDVB fix this. It seems that there is a memory leak somewhere. now I'm testing v 24.1, will post a picture if see the same problem

.

Posted: Thu Dec 03, 2009 12:08 pm
by Prog
What time request for that?

Posted: Thu Dec 03, 2009 12:30 pm
by hosavag
Did you mean how much time is required for ProgDVB to get such memory ? I do not remember exactly, about a couple of hours. Will try to monitor and get exact time.

Posted: Fri Dec 04, 2009 8:53 am
by hosavag
Tried to get that all the evening yesterday but the memory usage did not grow more that 240 MB, so either the problem is fixed in 24.1 version or it was a video codec problem (I had changed it also).