Community
Participate
Working Groups
Sometimes after I refresh my source tree (eg. after I update it outside eclipse using command-line SVN) eclipse loops forever on a system task labeled "System: Decoration Calculation - Calculating Decorations: Decorating" (see attached screenshot for an example). When this happens, eclipse eats lots of CPU (50-100%) (gkrellm shows load average of 2.5 -- screenshot attached). Cancelling "build workspace" task is ineffective, and only option is kill Eclipse -- which sometimes doesn't help at all because problem resumes as soon as eclipse restarts.
Created attachment 52398 [details] Screenshot of Eclipse task list
Created attachment 52399 [details] GKrellm showing CPU usage and load while Eclipse loops
Is this just with the SDK or do you have other plug-ins? also which decorators are enabled? If we get constant decoration requests from viewers this is likely to happen so we need to know which viewers and which decorators are enabled. A way to test the issue is to close viewers or turn off decorators one by one until the problem stops.
Hi Tod, my installation is minimal for my needs: eclipse-platform, eclipse-JDT, subclipse plugin (1.0.3 -- version 1.1.x is still too buggy to be used). ... I don't really know what decorators are, sorry =) (first time I heard of it was when I traced the source of the problem at hand) So: what are they, and how do I turn them off? (I will try closing views anyway whenever it happens again).
Look in Preferences->Label Decorations you can enable or disable them there. I am suspicious of your repository provider.
Thks, found it. Yes, it could be SVN related -- it has been reported by one of my coworkers that disabling/removing subclipse solved the problem at least once. This is obviously not a solution... But, what do you mean exactly? I mean, what could be the problem? It's a SVN server v1.3.2, I guess, running on Linux, and I am accessing repository through HTTPS. Could it be SVN fault? Even if so, shouldn't eclipse handle it in a more graceful manner?
The problem is that they are flooding us with decoration requests due to constant label updates. We could implement something that turns decoration off if the DecoratorManager is flooded - I'll update the problem report title to reflect this. It is still an issue for Subclipse regardless - even with our decorations turned off they must be spending a lot of time in redundant label processing.
Mmmh... ok, now I see. Makes sense. I agree that making DecoratorManager more robust with regards to requests floods should make eclipse usable again under such circumstances. Also, the updated report title now makes more sense indeed. I am not sure I agree with severity changing to "enchancement", though -- as far as user perception goes eclipse is looping forever when this happens, and the only way to get out of it (aside from waiting "forever") is killing it. This doesn't sound like something that should only be "enhanced" (even though the cause of the problem is not eclipse itself but one of its plugins). Just my $0.02... Also, how should we deal with this regarding subclipse? Should I open a bug report with them about it? Will you guys do it? They should be focusing on the upcoming version 1.1.x, but hopefully they either release it as stable or fix the problem on 1.0.x trunk.
Makes sense
(In reply to comment #8) > Also, how should we deal with this regarding subclipse? Should I open a bug > report with them about it? Please open a bug against subclipse thanks. I agree it'd be good to throttle bad plugins abusing updating. Tricky problem and not for time remaining in 3.5.
Oleg is now responsible for watching the [Decorators] category.
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.
