Bug 513571 - AbstractReconciler.BackgroundThread consumes small amount of cpu while Eclipse is idle
Summary: AbstractReconciler.BackgroundThread consumes small amount of cpu while Eclips...
Status: REOPENED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-13 09:23 EDT by Marc-André Laperle CLA
Modified: 2020-05-12 02:55 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc-André Laperle CLA 2017-03-13 09:23:28 EDT
Using Eclipse 4.7-I20170210-0615
macOS 10.12.3

While Eclipse is in the background and is idle with a few editors open (Java, C++), I can see that it uses a little bit of CPU. If I look at the energy impact in Activity Monitor it'S around 2-3.0 depending on the number of editors open, which is often the highest value of the system while it's idle. I profiled this and found a few threads running periodically. One of them is AbstractReconciler.BackgroundThread which runs every 500ms by default.
I'm not sure why it needs to run every 500ms. I think there should be a way to make it wait forever until either cancellation or a dirty region is queued.

I haven't checked on other platforms than macOS they are likely affected too.

One thing to note is that I've seen small CPU consumption while idle for years so I don't think it's a recent regression.
Comment 1 Eclipse Genie CLA 2020-03-16 10:32: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.
Comment 2 Marc-André Laperle CLA 2020-03-21 14:02:06 EDT
Still true
Comment 3 Lars Vogel CLA 2020-05-11 15:53:35 EDT
Please reopen if the problem still persists.
Comment 4 Marc-André Laperle CLA 2020-05-11 22:15:34 EDT
It does