Summary: | Cancel build with 10000+ problems takes forever to update (1G2Q9YZ) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jerome Lanneluc <jerome_lanneluc> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | VERIFIED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | Keywords: | performance |
Version: | 2.0 | ||
Target Milestone: | 2.0 F2 | ||
Hardware: | All | ||
OS: | Windows NT | ||
Whiteboard: |
Description
Jerome Lanneluc
2001-10-10 22:20:14 EDT
PRODUCT VERSION: jabiru 24 It's unlikely that we will be able to fundamentally change the presentation of the task list in the near future. From the description it looks like the error markers were still generated in spite of the user pressing cancel. Not generating the markers would have a huge impact on the performace. Is this possible? Would it be possible to not populate the task list with errors if a build has been cancelled? Markers are created as errors are discovered. So I don't think it is possible. Assigning to Philippe for information. Markers already got generated when cancel is hit. The time is in the task list updating. Deferring, we would have to change the Java builder to work-around a slow task view. Closing, number has been reduced when classpath is broken, max problem per unit is also in. Last: task list can cope with large number of problems and will refuse to show them all. closing Closed Verified |