Community
Participate
Working Groups
I've been working with some active task and been writing code that generates lots of code (about 20000 new resources) within resources of some project in Eclipse workspace. To bring those resources into Eclipse I hit refresh and after that Eclipse died (somewhere in Mylyn code bouncing back and forth around adding new resources to its models). The worst part is that after killing Eclipse and restarting things things start over (because task activated automatically on startup) and it look like I will have to drop this Workspace and start over from scratch. So, data loss, hence a blocker severity of this issue. Perhaps the simplest fix for that would be to not activate task on startup (that is easy enough to do that from task history) or provide preference for that.
I don't think it's necessary to add a preference for automatic task reactivation. The described performance problem sounds very similar to a bug in the resource listener that has been fixed in the latest weekly build: https://bugs.eclipse.org/bugs/show_bug.cgi?id=245234#c14 . Usually it should not be necessary to disable automatic task activation but it can still be difficult to recover when this triggers another problem, e.g. opening a problematic editor or processing a broken context. To address that I have added a system property to disable task activation on startup: http://wiki.eclipse.org/Mylyn/User_Guide#System_Properties . I would prefer to couple this to the workspace state instead of using a property though. Task reactivation should be disabled if the workspace did not shutdown cleanly. Any idea how it is possible to detect that?
Created attachment 114367 [details] mylyn/context/zip
Personally I believe it is a bad idea to require user to specify system properties. They introduce global state and not exactly convenient to work with in RCP applications, such as Eclipse.
As per discussion on the last conference call: The system property will be replaced by a command line option, e.g. "-no-activate-task".
The command line argument will be available in the next weekly build: http://wiki.eclipse.org/Mylyn/User_Guide#Command_Line .
