flyswatta Wrote:I saw this exact problem while using vplug via the MultiDec plugin. You may want to make sure that you don't have any plugins installed.
That's interesting to know. As stated in my very first post in this thread, I'm not using any extra plugins though, so this wouldn't apply to me.
I also had this problem around six months ago so it's not suddenly a bug in GB-PVR as it was several versions previous to the latest. I wish I could have narrowed it down and solved it but it must just be XP x64 and its handling of large files.
Do you also see it happen with other things? For example, I mentioned I saw the exact same symptoms whenever I tried to burn an ISO. Maybe you could try that if you have the time. At least to put your mind to rest that it isn't GB-PVR. Burning individual files on the fly were fine but one large DVD (~4.3GB) causes the memory problem. This is what leads me to believe it is the handling of large files in XP x64. Since GB-PVR can generate multi gigabyte files it isn't hard to see the connection. Once the recording of these stops, the memory is freed except all your basic processes have been forced into the pagefile. If I remember correctly, I think I also saw slowdowns when copying or moving large files from one drive to another.
2008-01-05, 11:08 PM (This post was last modified: 2008-01-05, 11:23 PM by Ommina.)
Is there some sort of amusing write-caching going on, that is storing the recording output to memory and only dumping to disc at the end?
Also - you can select "all instances" for processes in perfmon. You'll get a lot of lines, but if one is increasing dramatically as recording continues, it will be obvious enough.
Ommina Wrote:Is there some sort of amusing write-caching going on, that is storing the recording output to memory and only dumping to disc at the end?
It seemed that way. However, XP x64 is long gone from my system and I don't intend on reinstalling it to find out. I wasted far too much time on the little bastard trying to figure just this one problem out. I'm just going to label it as 'broken' and ignore it, especially since Vista handles memory so much better.
_gl Wrote:Try disabling your virus scanner. It may be scanning the file and never releasing the memory.
Yeah, I wondered about this also.
Finding out which process is actually using this memory would go a long way to determining this. So far we dont know fo show. It happens while a recording is occurring, but that doesnt mean it is recording service. It could easily be the virus scanner monitoring the growing file, or some other process all together.