Community
Participate
Working Groups
At times, the appearence of vertical scroll bars in Eclipse cause the CPU utilization to stay at 100% infinitely. The vertical scroll bar also stops to work, in particular dragging will make the scroll bar jump up and down erratically, restoring its position to the original one. This does not immediately stop everything from working, but Eclipse definitely gets much slower. Some functions appear to stop working when in this state, in particular Ctrl-C (copy) does not work in the editors. Also, launching program runs and Ant builds hang when the progress dialog appears. I've only seen it happen with Eclipse 2.1 on Linux with GTK2. I run Gnome 2.2 on a Gentoo Linux system. ACTIONS TO REPRODUCE: I've not been able to reproduce this behaviour 100%, although it is happening very often currently. Typically it occurs directly after launching Eclipse if the JDT resouce tree (to the left) had enough items open to cause the tree view to display the vertical scroll bar. It also happens in some dialogs using scroll bars, such as the "Run Ant..." if too many targets are available in the build.xml. WORKAROUND: The CPU activity can be restored to normal levels by closing items in the tree view so that the scroll bar is removed. Reopening the items thereafter cause no problems, so it seems to be related only to the initialization of a new scroll bar. If there are no items to close in the tree view (or if it is a list view), clicking the "^" button at the top of the scroll bar a few times may also work. SUGGESTIONS: This looks extremely much like a UI- or event thread is hanging in a tight loop. My guess is that it is releated to GTK2, as I've never seen this in Eclipse on Windows. I also assume that the problem lies in the code that initializes the GTK+ scrollbars. It may of course also be some bug in GTK+ that very few other applications expose.
it's a bug in GTK, please take a look at Bug#36698 Note: bug number mention above teach you how to patch GTK for mandrake and redhat linux (i don't much about Gentoo linux and its versions), but I still believe that after reading the bug36698 you will be able to figure out how to workaround this bug in Gentoo, if you do so please fell free to add any information to the bug so it can help other Gentoo users. Thanks *** This bug has been marked as a duplicate of 36698 ***
Many thanks Felipe, I found a patch for this in Gentoo also. (Not marked stable yet, however, grr...)
*** Bug 38301 has been marked as a duplicate of this bug. ***
