I'm using ProgDVB with DVB-T and it increases it's memory usage with 1 MB per second. When it's about 700 MB, the whole application slows down and picture/sound interrupt. Had the same problem with an older 5.12 version. I have timeshifting set to "file", so this won't be the problem. Any ideas ?

Please add your technical details, on DVB device, computer system and OS.

If that would be a general problem, I must have had this here as well.

To exclude time shift as a cause, you may want to reduce the size drastically or even reinstall with timeshift=none.

And make sure, this is not caused by a plugin. Deactivating is not enough to be sure, reboot machine and take out it's DLL before restarting ProgDVB.

DVB-T Device: Pinnacle PCTV Hybrid Pro Stick (320e), BDA Driver
Computer: AMD Sempron 2600+, 1GB Ram
OS: WinXP SP2

Installed plugins: none

Just tested the latest 4.8 and it did not have the memory leak (it constantly uses 55 MB).

I tried to set the Time shift buffer to 10 MB and the problem still occurs.
The memory usage goes down to 90MB when I change the channel.

Next I did a new install to a new folder and the problem was mostly gone (memory usage increased by 50kb/s). I compared the two folders and found differences in ProgDVB.ini:
The problem seems to happen with "UseVMR=0", the new install has "UseVMR=2".

At least this is a hint.

VMR are renderers, in video settings.
They are depending on Windows very much, as in fact they are components of those.
I don't have XP, but perhaps there are some DVB related patches you would need, but that are not installed automatically or proposed by Windows Update.

Some similar aspects have already been discussed here, happy hunting...

A tiny rise in memory usage is normal, due to EPG, TXT (if loaded before) and alike.
AFAIK latest 5.12 versions are storing EPG into a file instead of RAM.

Thanks.
I'm using WinXP SP2 vanilla, meaning I'm refusing Microsoft updates ... maybe that's the problem. I'll try Microsoft's updates when I set up my machine next time.

Problem is when installing Microsoft Netframwork 3.5.....when downgrade on 3.0 ..is ok