| Summary: | [About] About -> Installation Details hangs the UI | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Gary Karasiuk <karasiuk> | ||||||
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | remy.suen | ||||||
| Version: | 3.6.1 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | stalebug | ||||||||
| Attachments: |
|
||||||||
|
Description
Gary Karasiuk
Created attachment 182986 [details]
screen shot of UI Thread
I can attached a Yourkit profile of this UI hang, if you would find that useful. Let me know if you would like it. (It is only 1.6 MB). Susan, this looks to me like it's an issue with the implementation of p2's content provider, what do you think? Any updates? (In reply to comment #4) > Any updates? It would be useful to have more information. The Your Kit profile certainly can't hurt. Specifically, I'd like to know what query is being executed in ElementQueryDescriptor.performQuery, as this query seems to be taking all the time, and since we are only querying the profile's contents (vs. going to a remote repository), it's not clear to me why this should take so long. The installation details use the progress service's asynch content provider so that the UI will not hang as content is being fetched, so I'll also need to look at the use of the UI job here. Created attachment 186669 [details]
couple stacj traces
It has gotten much better in 3.6.2. The hang is down to 6 seconds. I attached a zip file that has two stack traces that were taken during the hang.
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. |