Maybe I am doing something wrong or I missed a setting or so but...
When I click the icon to add a new task or the icon to add a new subitem, it takes over 5 seconds before the task data window appears.
Using the INSERT key or the CTRL-INS key makes no difference.
(Running on Windows XP professional sp3)
Regards.
Hi Erwin,
Can you please attach your TaskCoach.ini file and an anonymized version of your task file (Help->Anonymize) to this bug report so we can investigate? Please also tell which version of Task Coach you are using.
Thanks, Frank
TaskCoach.ini fiel
TaskData.tsk
Frank,
I uploaded the requested files.
Regards.
Frank,
Whoeps, typed to fast.
Using the latest version: 1.2.26
Regards
Hi Erwin,
There's just two tasks in there, right? For me it works normal, i.e. the task editor opens immediately (and that's on a virtual machine running Windows XP). A few questions:
Thanks, Frank
Frank,
Was out of the office...
Thinking about the situation I recalled that I had installed Task Coach first as mobile and then as desktop. So, I uninstalled the app. and cleaned out the registry. Then I installed Task Coach again...
Online the speed is little better, about 2 to 3 seconds before the screen to appear.
I this testing I have used no attachments. I do not use self defined task templates.
Yes, I do use the classic Windows theme. Activating XP-theme makes no difference.
Regards,
Erwin
Hi Erwin,
Did you remove the TaskCoach.ini file? That is where Task Coach keeps its settings. The registry is only used by InnoSetup (the installer).
There may be something the TaskCoach.ini file that is triggering the slow behavior. So please do not remove the TaskCoach.ini file, but rename it. If starting without TaskCoach.ini file makes Task Coach faster, please attach the file to this bug report.
Thanks, Frank
The same happens to me in Ubuntu Natty 11.04. It takes half a second until the task editor opens, no matter if it's a new or an existing task. During this delay, one core of the CPU runs at 100%. (SVN version)
Have you considered lazy population of the task editor's tabs?
Also, just after upgrading to the SVN version, it appears that closing a task editor also eats CPU time.
@kirillmueller Yes, I have considered lazy population of notebook tabs but haven't implemented it yet because it adds complexity that I would rather avoid. But we may not have a choice. On the other hand, 5 seconds is so long that something else must be in play as well.
How big is your task file? (in terms of nr of tasks, categories and efforts).
Thanks, Frank
For me it's 0.5 seconds, but still too long.
The task file is just about 100 tasks, in hierarchies of up to five levels. Just a couple of categories.
I did some memory profiling using psutil. When creating a new EditBook, each new tab is eating at least 500k, and the page creation was also the time bottleneck. What is worse, the memory is not freed afterwards, not even after an explicit gc.collect(). This is just to tell that the performance issues probably coincide with the memory problems (e.g., id:3354000).
I'd vote for lazy population anyway. By using the right design pattern (a proxy?) the additional complexity can be hidden easily.
Edit: The 500k leak applies for the trunk version. The Release1_2_Branch version also seems to leak, but a lot less.
It takes 2 seconds to bring up the task edit window for me, and uses full CPU on one core while doing so. How long I've been running the program and how many tasks I have doesn't seem to affect the delay. (version 1.33 on Windows 7)
@tehalynn Do your tasks have attachments?
@fniessink Nope.
Jérôme, can you replicate this on Windows 7?
Thanks, Frank
Generally speaking, opening the editor dialog is painfully slow in 1.3 compared to 1.2, though I'm more in the 2s range, regardless of the platform. I also confirm the memory leak (at least on Linux). I tried disabling undo and explicitly calling Destroy() on the dialog but that doesn't fix it.
i'm using version 1.3.4 on windows 7 starter and it takes 5 seconds to insert or open a task, which feels painfully slow. I renamed the ini file and it was still over 4 seconds. My task file is has about 300 tasks in it.
I've noticed that every time I press insert to add a task the memory usage for taskcoach.exe shown in task manager goes up by about 2mb, then when I close that new task the memory only goes back down by 1mb. so it just goes up and up. when opening an existing task a similar thing happens, but only by about 200k for each open/close. this is on windows 7 starter with 2gb ram.
any ideas / fixes?
Updating as not fixed. Yet another bug about sluggishness. Dealing with this really needs to be priority. I'm sure it turns off many new users.
Best,
Aaron
Hi Ernie, please try the latest version (perhaps even the bugfix version here http://www.fraca7.net/TaskCoach-packages/latest_bugfixes.py )
Several performance improvements have been implemented.
Let us know if you are still having these issues.
Thanks,
Aaron
This is definitely fixed, it was the recursive validation stuff in sized_controls.