ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE. Software > ProcessTamer

Discrepancy between GUI and tray

(1/2) > >>

I'm confused by an apparent disconnect between what's going on among the tray app, the GUI, The Windows Task Mgr, and a utility called FreeMeter. For example, for the last several minutes the tray has said winlogon.exe was being tamed, but the GUI said it was using 0/0 CPU. Also, FreeMeter usually shows a far higher CPU rate than the percentages in GUI. FreeMeter sometimes is consistently at 100% but the GUI shows very low CPU utilization  and nothing is tamed even after a long wait. This is even after adjusting the slider control almost halfway.

What accounts for the wide discrepancy? In the end what I care about most is whether my system is bogged down, but this is puzzling.

I'm using v2b6; might b8 be different?

Just now the tray said AutoSave.exe was being tamed. The app wasn't doing anything, the GUI said 0/0, and the log indicated that opera.exe had been tamed and untamed (which makes sense, since Opera is the app that often bogs down).

Just confirmed this quirk. Started CPU eater. The tray says AutoSave.exe was being tamed, while the log correctly said CPUEater.

ah ok, the tool tip in the tray seems to report the wrong programs sometimes; i am going to work on fixing the tooltip today.

thanks longrun.

looks like that log feature is helping out already :)

btw you can see the effects of the slider by watching the different between Instand and Average CPU readings.  the more to the left, the more AVG will rapidly track Instant.

draggin a window around the screen quickly will increase cpu usage temporarily and help to demonstrate differences.


[0] Message Index

[#] Next page

Go to full version