Bugzilla – Full Text Bug Listing
| Summary: | Progress View Hang on startup | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | David Williams <david_williams> | ||||||
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | ||||||||
| Version: | 4.2 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | stalebug | ||||||||
| Attachments: |
|
||||||||
Created attachment 210024 [details]
three stack dumps taken a minute or so apart while in "hung" state
FYI, observed using Linux, 64 bit, using 1.6 JRE.
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. If the bug is still relevant, please remove the "stalebug" whiteboard tag. |
Created attachment 210023 [details] layout showing progress view "hung" In testing I20120123-2200 I saw one situation where the progress view appeared to "hang" on "Initializing Java Tooling ... Configuring Search Engines". I seemed to occur consistently when the progress view was "on top" of the Package Explorer (when shut down, so it was there when restarting). I'll attach screen shot to be clearer. I normally don't have it there, and if it was at bottom of that pane or the long pane at bottom, this apparent hang did not occur ... as if z-order mattered, or something. I call it "apparent hang" since a) processor doesn't seem all that busy as it might in infinite loop or net access and b) if I click on "remove finished processes" the "in progress" task goes away. I'll also attach stack dump, taken a minute or so apart, in case that helps identify why it is not finishing on its own.