HI,
I am not sure if it is only my problem, but in new version 0.78.0 when I click on task snooze (on OK button) it take about 1 minute to continue and during this time is task coach frozen.
It also happen when I click on the task name in reminder windows (to open the task), it take about 15 seconds. Also when I create a new task and click on OK then happen the same. It was OK in version 0.77.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems it happens with every change. I now changed the category by right click menu and it was 20 seconds frozen and the cpu was 100%. I have enabled save after every change.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
you are right. It seems to be connected with the save function. When I disable autosave then I am able to work with taskcoach very quickly and wihtout issue. Then when I click on Save in menu it take 100% cpu and 20s econds of time (taskcoach is frozen). Otherwise I have to have the autosave enabled. Please can you help me what I should do to have it solved?
Thanks a lot
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I craeted new file tsk and tested the save function for 3-5 tasks and it is ok. In my TSK file I have about 100 tasks. But in version 0.77.0 was everything working :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
solution with INI I tested, because I made completely uninstallation of taskcoach, removed all data application etc., but removing ini doesnt help. however second solution seems to be the right way. I removed all backups and now the save function seems to be ok. Do you think it is connected with thee new backup solition when not all backups are kept? I will test it today and let you know
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think the performance issue only happens when you have a lot of backup files. Release 0.78.0 will not create a lot of backup files, so after you delete the backup files by hand, the issue should not return.
Cheers, Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A fix was made and checked into the source code repository of Task Coach. The fix will be part of the next release. You will get another notification when that release is available with the request to install the new release and confirm that your issue has indeed been fixed.
This bug should be fixed in the latest release of Task Coach. Can
you please install the latest release of Task Coach and confirm
that this bug has indeed been fixed?
Thanks, Task Coach development team
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It also happen when I click on the task name in reminder windows (to open the task), it take about 15 seconds. Also when I create a new task and click on OK then happen the same. It was OK in version 0.77.0
Task removing do the same (15 seconds freez)
It seems it happens with every change. I now changed the category by right click menu and it was 20 seconds frozen and the cpu was 100%. I have enabled save after every change.
Hi,
It's probably the saving that is slow. Does it help to turn off autosave?
Thanks, Frank
Hi Frank,
you are right. It seems to be connected with the save function. When I disable autosave then I am able to work with taskcoach very quickly and wihtout issue. Then when I click on Save in menu it take 100% cpu and 20s econds of time (taskcoach is frozen). Otherwise I have to have the autosave enabled. Please can you help me what I should do to have it solved?
Thanks a lot
I craeted new file tsk and tested the save function for 3-5 tasks and it is ok. In my TSK file I have about 100 tasks. But in version 0.77.0 was everything working :(
Have you tried removing your TaskCoach.ini file to see whether that helps?
Thanks, Frank
Hi,
Please remove all backup files that are in the same folder as your task file. I think that might help.
Thanks, Frank
Hi Frank,
solution with INI I tested, because I made completely uninstallation of taskcoach, removed all data application etc., but removing ini doesnt help. however second solution seems to be the right way. I removed all backups and now the save function seems to be ok. Do you think it is connected with thee new backup solition when not all backups are kept? I will test it today and let you know
I think the performance issue only happens when you have a lot of backup files. Release 0.78.0 will not create a lot of backup files, so after you delete the backup files by hand, the issue should not return.
Cheers, Frank
I can confirm that the issue is solved
A fix was made and checked into the source code repository of Task Coach. The fix will be part of the next release. You will get another notification when that release is available with the request to install the new release and confirm that your issue has indeed been fixed.
If you like, you can download a recent build from http://www.fraca7.net/TaskCoach-packages/latest_bugfixes.py to test the fix.
Because a fix has been made for this bug report, the priority of this report has been lowered to 1 and its resolution has been set to 'Fixed'.
Thanks, Task Coach development team
This bug should be fixed in the latest release of Task Coach. Can
you please install the latest release of Task Coach and confirm
that this bug has indeed been fixed?
Thanks, Task Coach development team
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).