Hi, first of all thanks for a great app!
I have a problem with my current version (1.4.6), the app works perfectly when you use it but if you keep it opened for some time (I don't know if it is timed or linked to the screensaver or ?!) it starts to use a full core of my CPU (in my case the CPU goes from a few % when I use the app to 25% - a full core - when I don't use it). This is typical of apps mining coins in the background. Is it the case with Task Coach?
There's no way Task Coach is mining bitcoins (unless some crazy chance you somehow downloaded a hacked version from some other source). I assumed this was a hyperbole to just complain about the CPU use.
Given the open-for-some-time issue, perhaps this is a file that is getting bloated in its delta file. Try closing Task Coach, deleting any .tsk.delta files and then re-opening. If it still has this issue, try renaming (or just deleting) the .ini when Task Coach is closed and then re-open. See https://answers.launchpad.net/taskcoach/+faq/1061
If there's still issues, it may relate to the outdated libraries, but I'll have to then see if Jerome can help investigate further.
Thanks Aaron, I have checked the SHA-1 of the install file (TaskCoach-1.4.6-win32.exe), it is the same as the one displayed here (https://sourceforge.net/projects/taskcoach/files/taskcoach/Release-1.4.6/). I'll try to delete the delta and ini file and monitor what happens next.
I have deleted the delta files. I think the 25% happen after hibernation or >1 hour without user input on the machine. I'll let you know if this happens after the delta removal.
One thing that may or may not be related, I have errors in the log:
Connection to what?!
Deleted by OP. Not relevant to current case.
Last edit: valten 2019-10-09
Deleted by OP. Not relevant to current case.
Last edit: valten 2019-10-09
Deleted by OP. Not relevant to current case.
Last edit: valten 2019-10-09
Back to the original issue: I can confirm that putting my windows 7 PC in hibernation (where it saves to disk) while task coach is running and then waking it up, triggers the 25% CPU issue.
Are you suggesting that it isn't a problem until suspend, and then something about waking from hibernate causes the CPU issue?
If so, does it then clear up if you close and re-open Task Coach?
1- "something about waking from hibernate causes the CPU issue" Yes.
2- "does it then clear up if you close and re-open Task Coach?" Yes, back to normal (<1%)
3- " it isn't a problem until suspend" I am not 100% sure that only hibernate triggers the condition. I will do more test.
Last edit: valten 2019-10-09
I made another test by putting the PC in sleep mode (not hibernate) and I also get the CPU issue.
Note that locking the session down with Win+L and logging back in does not lead to the issue (CPU stays low).
Assigning to Jerome. I don't know if he'll figure out to do anything though. It may be that we just chalk this up to the need to update our frameworks still. That will fix many things once we finally get to it.