| Summary: | [Decorators] Thread blocks at start while adding decorations | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Marc-André Laperle <malaperle> | ||||
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||
| Status: | CLOSED INVALID | QA Contact: | Oleg Besedin <ob1.eclipse> | ||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | ob1.eclipse, pwebster | ||||
| Version: | 3.6.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Marc-André Laperle
Created attachment 181659 [details]
stack
(In reply to comment #0) > Build Identifier: 20100917-0705 > Sometimes, when I start Eclipse, a thread will block and use all the CPU until > I restart Eclipse. I don't see a deadlock in the attached stack. In the attachment both "main" thread and "worker-0" threads are waiting on the "worker-11" thread which is running (see references to 0x19ef3370). So, from this stack itself it does not look like a deadlock, but probably a case of too many decorators or decorator processing taking too long. Or a resource tree for the workspace being broken and containing a cycle. > ... I have the Perforce plug-in and CDT installed ... To help find the problem: - Do you see a deadlock in other stacks? If so, can you attach one? - Do you see this problem using a minimal workspace, something akin to "Hello World"? - Does the problem happen with Eclipse SDK itself? if not, how about Eclipse SDK + Perforce and Eclipse SDK + CDT? I know this is a lot of questions, but the attached stack really does not have enough information to narrow down the issue. (In reply to comment #2) > (In reply to comment #0) > > Build Identifier: 20100917-0705 > > Sometimes, when I start Eclipse, a thread will block and use all the CPU until > > I restart Eclipse. > > I don't see a deadlock in the attached stack. In the attachment both "main" > thread and "worker-0" threads are waiting on the "worker-11" thread which is > running (see references to 0x19ef3370). Thanks for explaining. I understand stacks better now. > > ... I have the Perforce plug-in and CDT installed ... > I know this is a lot of questions, but the attached stack really does not have > enough information to narrow down the issue. I will do more testing, thanks for the suggestions. I am under the impression that either the Perforce plug-in and/or the Perforce server might be the problem. I will change this to invalid if I can confirm that. I haven't been able to reproduce the problem. I will assume it's decorator processing taking too long because of a server slow down. |