Bugzilla – Full Text Bug Listing
| Summary: | 5+ second UI lockup in MarkerManager#doFindMarkers | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | James Blackburn <jamesblackburn+eclipse> | ||||||
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | yevshif | ||||||
| Version: | 3.6 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | All | ||||||||
| Whiteboard: | stalebug | ||||||||
| Attachments: |
|
||||||||
Created attachment 167678 [details]
stack 6
Moving to resources as restarting the Eclipse seems to fix the issue. 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. 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |
Created attachment 167677 [details] stack 1 Having run Eclipse for some time (1 week+), a user noticed the UI become slow on saving files. The busy cursor is present for long enough to switch to a shell and run 'jstack' against the running eclipse java. We ran jstack in a while loop with 1s sleep between each invocation. What we found was up to 5+s of time spent fetching markers in Team UI. This could be an issue in core.resources markers handling... We believe the total number of markers should be relatively consistent. First and last backtrace attached: 2010-05-06 17:30:44 2010-05-06 17:30:50 UI was busy for 6 seconds with the same main call-stack in all the backtraces in between. Once the problem occurs it occurs reliably. Restarting Eclipse resolves it.