Recording Service memory leak?

[djtaylor]

Buy more memory

How much memory do you suggest?

This is a rhetorical question. There's no point simplly throwing memory at it since it grows linearly at around 4KB/s (as observed) when recording. I know that Sub doesn't use any plug-ins and thus says he doesn't experience a problem therefore I for one respect that and will deal with it myself.

Clearly something is continually leaking such that the only way to clear things out is to restart the recording service. When i'm away from home, this thing goes into gigabytes ov VM, Windows complains that the machine is low on VM and extends it but it's not a great situation.

My box already has 1GB, sure I could throw in another 1 or even 2GB but throwing in memory at a coding problem is just plain wrong and is just sadly the solution to too many coding issues these days, throw CPU and memory and the problem is merely masked, bit like spraying air freshner into a room full of farts.

All that adding memory would do is delay the problem by a few days.

David.

[smeghead]

Apologies - I was being sarcastic.

I know it's drastic but have you tried a fresh windows install with a fresh install of gbpvr. Back up the gbpvr.mdb and config.xml plus any other changes. If all is OK then add in your extra utils (and .bat file changes) one at a time.

[djtaylor]

Apologies - I was being sarcastic.

I know it's drastic but have you tried a fresh windows install with a fresh install of gbpvr. Back up the gbpvr.mdb and config.xml plus any other changes. If all is OK then add in your extra utils (and .bat file changes) one at a time.

Don't worry about the sarcastic thing, I'm English, i'm expert at it My response was as much an explanation.

To be honest, i'm not going to do anything to attempt a fix because it was a fresh XP install dedicated only to GBPVR and it's solely an issue surrounding this and the bits installed with it. There's not much point disabling bits to find out which one it is because which ever one it turns out to be, I still want it.

I don't doubt that with no plugins there's no problem but I want the plugins so i'll live with it. I've done technical support for every version of Windows from 1.0 onwards (including DOS 1) so I'm quite familiar with Microsoft OS's, I'm getting old, I don't care, the fix is to to just keep an eye on it and kick it from time to time.

David.

[cosmocat]

FWIW I'm also getting a memory leak same as djtaylor.
If watch the processes wityh Task manager I can see the recording service memory constantly climbing, and never going down. My GBPVR server runs 24x7 and after about a week the the recording service was allocated 330Megs of memory and windows was complaining of low VM. Restarting the recording service restored things to normality bbut the recording service RAM starts climbing again.

I was going to set a scheduled task to restart the recording service every 24Hours ( at about 5AM ) as a work around.

The machine was a fresh install of XP+SP2 with 1GB of RAM.

[djtaylor]

I just wanted to come back to this because yesterday, I disabled the plug-ins using the single check box to do so in the config app.

Today, I find that the recording service has grown from 25MB to 350MB.

Something would appear to be definitely leaking memory.

David.

[sub]

I have found and fixed a memory leak in the next release. This memory leak only affected DVB users.

You could try setting the <BDAUsePsiParser> setting to 'false' to see if it helps.

[djtaylor]

I have found and fixed a memory leak in the next release. This memory leak only affected DVB users.

You could try setting the <BDAUsePsiParser> setting to 'false' to see if it helps.

Excellent news! I have three DVB-T tuners.

Sorry to ask the obvious question but what does that setting do, will I lose anything, what's the consequence?

David.

[sub]

Ideally I like the setting left on, but if this problem is causing you grief, you can disable it. With is disabled you shouldnt rescan, and you wont be able to get EPG updates.

[djtaylor]

Ideally I like the setting left on, but if this problem is causing you grief, you can disable it. With is disabled you shouldnt rescan, and you wont be able to get EPG updates.

Not a problem, I can't use broadcast EPG updates anyway because too many channels don't get the info ever, like TMF and The Hits despite the Hauppauge software picking something up.

Looking forward to the version of gbpvr that sorts the memory issue out.

EDIT: After an evenings recording with that value set, result is no bloated recording service
Thanks

David.

[Ecthelion]

Hi,

I just wanted to confirm that I have observed this too. I had the recording service record two films during one night and found that the next morning the memory consumption had risen from ~40MB to more than 200MB. There was no EPG update or GUI usage during that time.

FYI, with the latest version, 09707, the memory leak does no longer occur on my machine. When installing the new version, the WDM recorder plugin was removed, so that the leak might have been due to the plugin (although I did recordings from DVB-T source) or due to a bug in the previous gbpvr version.