CaptureGenPCI.exe useing 101 megs of ram in background

[nacho32]

I noticed this in task manager when I'm not even watching TV and have the tray icon off and the IR blaster off but i see C:\Program Files\WinTV\TVServer
CaptureGenPCI.exe
running in the background using 101 megs of ram running the latest version of wintv

[Mr X]

which card is that?

[nacho32]

WInTV 1600 - 74041 LF REV.C6B2 pci card has the same yeild on both WIn 7 32 bit and win xp 32 bit on my quad Boot system, both draw 101 megs of ram.

[nacho32]

and I reverted back to 24c same results

[nacho32]

have a field day

[Mr X]

this is normal. A single tuner device uses around 50Mb and two tuners 100Mb (The HVR-1600 is a combo device so Analog is seperate from the Digital Tuner)

[nacho32]

well back to squire 1, why is it drawing this ram when not in use? is their a service I could turn off to manual upon start up?

[TheNewGuy]

and I reverted back to 24c same results

It's always been this way, so going back to the previous version wont make any difference. The exact amount of memory used varies quite a bit depending on the device. Its basically using this ram because of all the directshow framework and components are loaded into memory, and the requirements of the drivers. Its quite time consuming for all this stuff to be loaded and setup, so the background service has historically done this setup once at startup so that live tv and recordings can start in a timely fashion. It'd be nice not to use that much memory all the time, but there isn't anything we can do about it easily.

With re-engineering of some (very old) Hauppauge code, we could reduce it a bit, but I'm not sure if it's worth it. The reality is that if you're not using the app, then Window's is just going to swap it out to disk if it needs the memory elsewhere. Its not going to lead to Windows running out of memory. Given it's not been causing issues, and we're short of available development time, and with other more important projects demanding time, its unlikely we'll be able to do anything about it in the near future. Sorry. I agree it's not ideal though, and I will keep it in mind for when we tackle WinTV8 in the future though.