Hi,
After I upgraded TC some months back (I hadn't upgraded for quite some time), it got reaaaly slow (around 10 - 20s) when adding changing dates / times in efforts. After moving TaskCoach.ini and restarting it works fine. I have 2 effort-viewers + 2 task-viewers running. When configuring it like that it is still fast. As soon as I quit TC though, the .ini file gets created. When TC starts again using that .ini file, it is very slow again.
I'm running debian testing/unstable.
TaskCoach.ini
Hi again,
Is any more information needed? Or would it be helpfull to attach my task-file as well? I can't use TC at the moment as it got too slow. So help is very welcome :-)
The task file would help (anonymized eventually), thanks.
anonymized and gziped TC file
e.g. editing an existing effort and just clicking on "Start tracking from last stop time" takes around half a minute to succeed. System is a dual-core with 1.6 GHz and 1.5 GB RAM free. At the time I click "Start tracking..." taskcoach eats up one cpu for that half minute.
Has somebody been able to reproduce this bug? Or is more information needed? If there's some other tests I can run please let me know...
I found out the problem but fixing it causes another one. Should be fixed soon though.
any progress? If there is a beta version or so I'll be happy to test it :-) .
Still haven't figured out a way to have the best of both worlds. Still working on it.
Hi again. Even if the bug is not yet fixed in a perfect way I would be happy if I could get any version running with my taskfile again. I don't mind if something else - which may not be essential for me - breaks.
So - if there is a branch I could checkout or if you could send me or attach a patch I would be very greatful!
warm regards,
Tom
The latest build (http://www.fraca7.net/TaskCoach-packages/latest_bugfixes.py) should fix the performance issue when running but it's slow as hell when closing the file.
We believe this is fixed. Please try the latest version and let us know if you still have trouble. There have been many efficiency improvements (and more to come in the next update).
Cheers,
Aaron