NextPVR v5.x memory leak?

[sub]

I suspect your machine isn't running low on memory, so isn't releasing the memory to the operating system. It's unlikely this is causing any issues on your machine.

This is the way .NET web server applications behave by default. It can be made to behave more like you're expecting, with memory more quickly returned to the operating system, but it comes at the expense of performance. Unfortunately this is a compile option though, so not a setting can put in a config file, so if I change for you, them I'm changing it for everyone.

At this stage I think it's probably preferable to leave it in the default configuration. The memory is still released to the operating system if required, but is there for best performance if the application needs it.

[sub]

Over the last couple of hours I've done a dozen or so EPG updates in the profiling dev tools, and I'm confident it's not leaking anything. I've also tested that compile setting on and off, and seen the different in behaviour both ways, so I'm comfortable that it's behaving in the way I described above.

[terabitz]

Perhaps memory leak was an incorrect assessment on my part and I was just not aware of how it handled memory allocation due to tasks like the EPG update. My mistake.

[sub]

No worries, it was worth me double checking this stuff.