Bug 420702 - [Decorators] Decorator manager delays image rendering even if element has no contributed decoration
Summary: [Decorators] Decorator manager delays image rendering even if element has no ...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: performance
Depends on:
Blocks: 416354 419906
  Show dependency tree
 
Reported: 2013-10-30 04:18 EDT by Dani Megert CLA
Modified: 2020-03-12 07:44 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2013-10-30 04:18:57 EDT 
The decorator manager delays icon decoration even if element has no contributed decoration.

We enabled decorator contributions for the JUnit view by using
PlatformUI.getWorkbench().getDecoratorManager().getLabelDecorator();
(see bug 416354). This caused the test result decorations in the JUnit view to lag behind the actual state (bug 419906).

Since no decorator was contributed, there should be no performance impact on the JUnit view's image rendering (label provider).
Comment 1 Dani Megert CLA 2013-10-30 04:19:23 EDT 
Note: This is not 4.x specific - same issue in 3.x.
Comment 2 Markus Keller CLA 2013-10-30 13:55:54 EDT 
The shared global queue also doesn't make sense. Why should my viewer have to wait if there are other viewers in the system whose decorators are slow?
Comment 3 Eclipse Genie CLA 2020-03-12 07:44:59 EDT 
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.