Serious memory leaks in Recording Service with 1.1.5

[sub]

Nothing springs to mind. Its may be to do with your ATI 550 drivers.

[sub]

Its funny that your graph's working set and virtual bytes dont show that process using all the memory. Are you sure its not another process using it? The 'available MBs' is definitely reducing, but this is a global value rather than something monitoring GBPVRRecordingService.exe usage. The virtual butes for that process seems to stay about constant.

[BotLogic]

Its funny that your graph's working set and virtual bytes dont show that process using all the memory. Are you sure its not another process using it? The 'available MBs' is definitely reducing, but this is a global value rather than something monitoring GBPVRRecordingService.exe usage.

As per my knowledge, all I can say is there is no other process tied to the recording service, and no other process was running 'just' for the duration of the recording. The recording was performed when the system was not in use for a while, and no other background tasks were active.

[sub]

Try using perfmon to graph the memory usage of each process to help narrow down what is using the memory.

[BotLogic]

Try using perfmon to graph the memory usage of each process to help narrow down what is using the memory.

While doing a recording, I've looked at each running process under Processes in Task Manager. There isn't any process whose memory usage balloons.

[sub]

The process tab in task manage isnt a good place to monitor memory usage. You'd be better graphing it in perfmon.

[BotLogic]

The process tab in task manage isnt a good place to monitor memory usage. You'd be better graphing it in perfmon.

It seems quite tedious to graph the memory usage of all processes, also taking into account that the stated memory usage of any one process never goes over 100 MB. The issue clearly is with the recording service or .NET or the card drivers.

[sub]

Ok, we'll leave it as an 'I dont know' then.

[Josef_K]

I used to have this very same problem when I used XP x64. I never did find the cause of it after months of research but it also manifested itself whenever I tried to burn a DVD. Try burning an ISO (full size ~4.37GB) and see if you experience the same issue. I believe it must have to do with a single large file endlessly being pumped into RAM. I also have 4GB and still had the same effect of everything hanging until it was done with the current operation. I have no idea why XP suddenly behaved this way. It was just working one day and then not working the next. This was on a fairly new install - maybe two or three months old at the time. XP x86 worked perfectly well before this, even minus the usual chunk of RAM x86 deducts.

As said above, I never did find the cause of it but I knew anyway that XP x64 doesn't sit nicely with 4GB RAM and with most of my customers coming to me with Vista, I decided to give up/format/reinstall so I could learn it better. This problem happened not long into the format/reinstall to initially put x64 on so I was reluctant to go through it all again once I'd set everything up the way I needed it to be. Vista handles memory much better. The only thing you need to remember to do is to switch all the themes, etc. to look like XP.

P.S. FYI, I have a Geforce so I would rule out ATI drivers.

[BotLogic]

I used to have this very same problem when I used XP x64.

Thanks. I intend to upgrade to Vista x64 and I can only hope that I won't have the same trouble then. I don't see why it makes sense, however, to switch Vista themes. I don't see what that has to do with anything.