Task view fills up and XMLBuddy hangs?
For one customer, the problem was that they used Perforce and/or manually copied files into their projects without doing a Refresh. Existing task view markers then couldn’t find the files, even though the names and paths are the same. That meant the the markers couldn’t be deleted. With auto-validation on, almost any change to a file would try to replace the task markers, which threw an exception. The user was in very bad shape, editing-wise. Always do a Refresh after changing project files outside Eclipse. We view the bad things that happened for lack of Refresh as an Eclipse bug, but it is easy to work around.
