CobianSoft

All of a sudden a Cobian.Reflector.Service.exe thread consumes continuously about 8% of CPU (see pictures). Looking at the Cobian UI Log tab no backup task is currently running. Strange is that not much is happening in the Process Monitor, just some threads create/exit. Can I do anything more for investigation?

If I stop the Cobian service via the Cobian Service Control this faulty thread keeps running. Then I can't start the service again as it says that is it already started (see picture). Looking at the Windows service manager the service state stays "Stopping...". Looking at the Windows event viewer there is nothing much neither in Application nor in System log.
The only way out is killing the service in the task manager (the service manager is not helping). After starting the service again it works well (no excessive CPU taken).

Interesting... I guess running in verbose log may show something of this activity... If no backup is running at all, my guess is that there is some thread that's stuck counting files... but why?

Does the verbose log log also activities outside of the backup task run? Is there at all any background service activity outside the scheduled backup tasks run (to be caught by the log)? Or do you mean a counting thread from a previous run?
Anyway, I will try the verbose log next time.

Yes, it should log everything outside too... Or I hope so..

"CPU consumed by a faulty thread" happened again a few times since my last post. Cannot find out what the cause could be. I set the verbose log but since the fault has nothing in common with backing up process (no backups are running at that time) the log is empty. I tried to stop the Cobian service via the Windows service manager. The manager starts stopping the service, a few threads under the Cobian service process are quit but the faulty thread remains constantly consuming about 8% of CPU (see the picture). The service manager than says it couldn't stop the service. The only way out of this is to kill the service process. The Cobian service manager doesn't help either. Any idea how I could find the cause?

Do you have any way to reproduce this? Have any backup been performed before the thread begins to spin?

If no backup is executed at all does this happens as well?

I have have my service running now about a week and don't see that behaviour....

I will be adding MORE verbose information in every thread for the next version in order to solve this issue.

I am using Ver 0.9.50 BETA and am seeing excessive CPU usage, for no reason since it isn't doing a backup, and the threads display shows a lot of activity.

If you had some task with non-ordinal days (First, Second, etc...) this should be solved in 0.9.55