Summary: | [Progress] Updating Progress view when there are a lot of jobs blocks UI/Main thread makes UI sluggish for minutes | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Raj Mandayam <ramanday> | ||||
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P4 | CC: | bokowski, john.arthorne, karasiuk, laffrac, panagiotis.korros, pombredanne | ||||
Version: | 3.2.1 | Keywords: | performance | ||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Bug Depends on: | 163245 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Raj Mandayam
2006-10-13 17:48:47 EDT
Created attachment 51987 [details]
progress view profiled screenshot
I agree that this is a bug in the progress view, but you are misusing it. The progress view is meant as a place for the end user to get an overview of background operations that are running, and to be able to cancel long-running operations if necessary. By starting 130 jobs, you are overwhelming the user and essentially making it impossible to see the other background operations that are running. You need to mark the 130 jobs as system jobs - see Job.setSystem() - this will remove those jobs from the progress view. Then, create a high-level job that is visible (and allows cancelling the 130 jobs is represents). Reassigning to inbox for further triage. This was a problem we noticed in a product based on WTP with a lot of plug-ins. The component that would create these jobs is called the validation framework. I beleive Gary Karasiuk has made some enhancements to the validation framework of this product (in its next version i think ?) since that time-period and maybe in a better position to say whether this problem still happens in that product's new version and/or if the product still requires a fix in eclipse. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |