Rivatuner Crazy Resource Usage Help

iode · **Memory**: DDR2 800 4GB 5-5-5-15

I am currently using Rivatuner 2.24 MSI Master Overclocking Area 2009 Edition and the resource usage is absolutely crazy. I am using it to overclock my graphics cards (SLI GTX260) and to adjust their fan speeds. I also have plugins that allow the monitoring of my Phenom II CPU (via Coretemp plugin). The Windows 7 gadgets on the right monitor are GPU monitors linked to Rivatuner. When I first start up Rivatuner, it uses very little resources, somewhere around 8,000K. However, after time, it increases little by little until it literally uses all 4GB of my RAM. In the time it took to write this question, it has increased to 169,122K. This is absolutely nuts and I don't know how to fix it. Please help!

5 Hours Later...

stangowner · 03-12-2010, 12:32 | posts: 562 | Location: MA

I'd try disabling any plugins for the hardware monitor, restart RivaTuner and let it run for a few hours. I suspect one of them may have a memory leak. I've never seen this issue with RivaTuner alone.

iode · **Memory**: DDR2 800 4GB 5-5-5-15

Quote:

Originally Posted by stangowner

I'd try disabling any plugins for the hardware monitor, restart RivaTuner and let it run for a few hours. I suspect one of them may have a memory leak. I've never seen this issue with RivaTuner alone.

Plugins currently enabled for Rivatuner are
ADT7473.dll
CoreTemp.dll
CPU.dll
NVThermalDiode.dll
SysMem.dll
VidMem.dll

Any hunches as to which I should disable or should I just go ahead and mass trial & error?

stangowner · 03-12-2010, 13:24 | posts: 562 | Location: MA

Disable them all, make sure the memory usage is fine (2-3 hours). Then enable them one at a time to find out which one. It should not take too long to start seeing a hike in usage (1 hour each or so).

fgw · 03-12-2010, 14:18 | posts: 103

agree with stangowner, and suspect one of the plugins having a memory leak. did a lot of plugin programming and can help with the following tip to check for such leaks:

a quick way to test for such memory leaks in plugins is to decrease "Data polling interval" which usually is set to 1000ms. by setting this down to 10ms you will make the plugins memory usage increasing 100 times faster.
deselect one plugin after the other while monitoring memory usage. memory usage will stop to increase after you disable the faulting pluging.
interesting to know which plugin it finally was ...