[eclipse-sig] [Bug 1294697] New: Eclipse consumes entire CPU as long as the window is open

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1294697

Bug ID: 1294697
           Summary: Eclipse consumes entire CPU as long as the window is
                    open
           Product: Fedora
           Version: 23
         Component: eclipse
          Assignee: [e-mail]
          Reporter: [e-mail]
        QA Contact: [e-mail]
                CC: [e-mail], [e-mail],
                    [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail]

Description of problem:
Eclipse consumes 80+ % of a CPU core when idle. Minimize the window and
CPU use goes to near zero. Maximize the window and it's back to 80+ %.
This is a great way to bleed a laptop battery dry in no time.

Version-Release number of selected component (if applicable):
Fedora 23 up to date as of 29 Dec 2015, 1800 UTC, kernal 4.2.8-300.fc23.x86_64
Mate Desktop 1.12.1
eclipse-platform-4.5.1-6.fc23.x86_64
java-1.8.0-openjdk-headless-1.8.0.65-13.b17.fc23.x86_64

How reproducible:
Installed F23, Mate Desktop, and *just* eclipse-platform on a VM. (Of course,
  the eclipse install pulled in all the usual supporting rpms)
Log in to a Mate desktop session, launch eclipse.
Observe high CPU use.
Always happens.
Same behavior observed on the host system.

Steps to Reproduce:
1. See above.
2.
3.

Actual results:
80+ % cpu use when eclipse window is open but otherwise idle (it's just
showing the welcome screen); minimize window, CPU % near zero; maximize
window, high CPU use again.

When CPU use is high, strace on the eclipse process shows:
[PolTec@raid-lvm-scratch Desktop]$ strace -p8507
Process 8507 attached
wait4(8521,

...and strace on java shows:
[PolTec@raid-lvm-scratch Desktop]$ strace -p8521
Process 8521 attached
futex(0x7f338b30e9d0, FUTEX_WAIT, 8522, NULL

top says it's java that's using up all the CPU time, almost like it's in a
spin lock waiting for something which never happens. So I suppose this could
be a java bug and nothing to do with eclipse.

Expected results:
Eclipse and java should be blocked and using no CPU to speak of when
there is no application interaction.

Additional info:
That's about it. Let me know if there's some way I can provide any
other info. If you just run top and start eclipse it should be
pretty blatant.