Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 89379

Summary:	[Markers] Problems view unresponsive during backsground CVS transactions
Product:	[Eclipse Project] Platform	Reporter:	Randy Hudson <hudsonr>
Component:	UI	Assignee:	Stefan Xenos <sxenos>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	Tod_Creasey
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Randy Hudson

2005-03-29 13:05:06 EST

My problems view never displays more than 40 or so problems.  Use of a Job to
update this table is overkill, and introduces unnecessary delays.

For example, I had a warning in file, I select Replace with HEAD, and then try
to go on to other problems in my project.  But, the problems view will not
update until the CVS job has completed.

Either the jobs should not block each other, or the problems view should not use
jobs until it is displaying enough items to actually benefit from Job use.

Comment 1 Stefan Xenos

2005-03-29 17:25:02 EST

The delay is due to the fact that the problems view doesn't process resource
deltas, but scans the entire workspace for markers (which can't happen while the
workspace is locked). Bug 84211 contains the start of a fix.

You are correct in that there are situations in which the Job is unnecessary,
but this has as much to do with the number of markers in the workspace as the
number of visible markers -- simply filtering down to the 40 markers you see in
the problems view is normally much too slow to do in the UI thread. 


*** This bug has been marked as a duplicate of 58836 ***