<solved> [NPVR 2.3.6] resource-exhaustion / memory leak

[ShiningDragon]

Yep, even with .ts files. The biggest waste happens, if you qeue the shows and play them one after one.
I have tested this now on my main machine (i5-2500k, 16 GiB RAM, 24 GiB swap, Win 7 x86_64) the same behaviour here.
LAV Splitter/ffdshow/AAC vs. microsoft ones (.ts files). No difference.

It makes even no difference if i qeue and let them play automatically or if i start exit start exit the movies manually.

[mvallevand]

NextPVR does need a lot of memory. I did some quick testing and memory does easily jumps up in large blocks there is OSD especially when I scroll the OSD guide over LiveTV video here for 1080i h263/ac3

Start in Guide 150MB -> 350MB video play - 700/800MB with the guide. -> 360 back at guide The garbage collection of the DS memory is really slow.

Testing the same steps with the NMT on the same channel, the PC memory effect is negligible.

100 > 106 > 107 ->104

Martin

[ShiningDragon]

Yep, the osd on sd material consumes ~25-30 MiB, but will be released after the osd disappears.

Startup ~150 MiB -> moving to video library ~230 MiB -> playback a x264 transcoded BluRay Rip ~430 MiB -> exiting playback -> 280 MiB.
I have "lost" ~50 MiB for only this step. Windows resource monitor tells me, that NextPVR.exe could free up max. 30 MiB, so where's the memory?

Ok, high memory usage and slow garbage collection isn't something new, that was in previous versions of npvr too. But there didn't happened any freezes. I know and "feel" that there's something wrong, but i can't point you two to the cause of this. I don't have any knowledge of programming.

[sub]

Can you post a perfmon graph showing the memory increasing over a few minutes while playing an individual file? Also post the npvr.log from the same session.

If it's not decoders, then this could only be related to OSD or subtitles, which are the only things that happen that consume a sizeable amount of memory.

[ShiningDragon]

perfmon graph offers a LOT of input, some special data fields i should observe?

[sub]

I'd probably add 'private bytes' 'virtual bytes' and 'working set' from the Process counters, for NextPVR.exe.

[ShiningDragon]

Here's a quick preview. I'll make a better one tonight on the mediacenter:

At ~20:32:40 i speeded up the measurement: i startet to skip the shows in 5 minute-steps, so that the difference could be make visible faster.
Attached is the log of npvr of this session.

[whurlston]

Windows 7 handles memory much, much differently from Windows XP. Watching the resource monitor. Does your "Available" + "Free" memory decrease much?

As for disabling the pagefile, that recommendation stems from the (incorrect) belief that Windows inefficiently makes use of the pagefile. There has been no conclusive proof since Windows 98 that disabling the pagefile is truly beneficial. This was true of XP and it's even more true of Windows 7. In fact, it can have negative consequences with Windows 7. A good read on the subject can be found at http://lifehacker.com/5426041/understand...disable-it

[sub]

I'm not really sure what to suggest. I've been trying to reproduce it here, but I'm not seeing the same behaviour.

Here is my graph, showing playback of a H.264 recording. The memory stays steady. The few spikes in memory usage happened when I moved the mouse over the screen and it showed the OSD, but they dropped back down when the OSD disappeared. The memory then dropped when the playback completed.

What video renderer are you using?

Have you tried changing video renderer or decoders (for .ts) to see if it helps?

[ShiningDragon]

I've been trying to reproduce it here, but I'm not seeing the same behaviour.

Mhm, even mvallevand experienced the same consumption like me. Curious.

The mediacenter, which started a few posts before, has stopped now. NextPVR has hung up itself. The physical memory consumption were not very high, but(!) the virtual memory part reached nearly 100%.
I am not sure what's happenig, but this wasn't definitvely until npvr 2.2.6 with latest hotfixes. Something has changed, one function is not compatible with our systems.


The red circled areas are the moment, where the video stops and NextPVR.exe were crashing (i was fast enough this time to prevent the mediacenter freezing).

I will now enable, but only for testing purposes, the swapfile on the mediacenter and repeat the playback of all simpsons episodes.

If the crash/freeze doesn't repeat, then we have to take a look on the virtual memory part of npvr, i guess.

Here is my graph, showing playback of a H.264 recording. The memory stays steady.

You're right, they are nearly perfect.

The few spikes in memory usage happened when I moved the mouse over the screen and it showed the OSD, but they dropped back down when the OSD disappeared.

The OSD is no problem after all on all my systems. It cost's around 25-30 MiB (but much enough for a small window with some letters. ;D) and frees up itself after disappearing.
I wouldn't blame the OSD for this memory leakage.

The memory then dropped when the playback completed.

And this doesn't happens on any of my machines. NextPVR.exe drops SOME memory, but not all. Every new file "eats up" around 30-50 MiB, which will free up again, if NextPVR.exe will be suspended.

What video renderer are you using?

EVR

Have you tried changing video renderer or decoders (for .ts) to see if it helps?

I tried the .ts files with the microsoft wmf codecs and with ffdshow. As splitter i tested haali and lav. No difference at all.

(...)

Thank you, whurlston. My missing programming skill doesn't mean that i don't know anything about pcs.

The cause for disabling the swap on this mediacenter has some causes:
1. Usage of a SSD to lower the write cycles.
2. Raise the usable space of the drive
3. Raise the bootup time (tested and confirmed)