[SOLVED] checkingprocessor.exe using 49% cpu

[sMax]

checkingprocessor.exe is using 49% cpu with no sources and no proxies in 4.2.5.. I have even pressed stop in the control tab.

please advise.

TIA.

 

[Hungry Bulldozer]

How many threads do you check proxy in?

 

[zeus]

facing the same problem.
already created a thread . link : http://zennolab.com/discussion/show...CPU-continuously&p=42087&viewfull=1#post42087

 

[sMax]

@HB: zero source reading threads, zero proxy checking threads. I'm not using proxies at all when this happens, and in the control tab I have stopped the processing with the stop button.


TIA

PS.
Ending the process in windows taskmanager will bring the process down to 0-1 % cpu usage but still 50,000k+ memory usage (and creeping up) for a process that is basically doing nothing( it might be looping to see if there is anything to process).

I guess the issue is at ZP startup this should not run or consume that much processing power when there is nothing to process.

Maybe a small driver that checks if there is any proxy to check and then starts this process is more appropriate.

 

[Hungry Bulldozer]

Guys we need logs of ZP and Wondows. Please send them to support email .

 

[sMax]

Don't know if this has been solved yet. But some additional info;

- this only happens if you are NOT using the proxy functions of ZP. So a viable workaround is to put in a source with a couple of (public) proxies and let it run, then processing is at most a couple of % and memory usage is under control.

Sent some windows error events to support email a couple of days ago. Hope that helped.

 

[rostonix]

Thank you