Community
Participate
Working Groups
Primary symptom: When closing Eclipse, even immediately after launching, and via either the Eclipse menu of the windowing system's title bar 'close' widget: * Eclipse hangs, after the progress indicator has 'filled', * Java starts using approx. 66% CPU, X-Windows approx. 33% (100% CPU, according to 'top'. My environment: RedHat Linux 7.1 (kernel 2.4.2-2) XFree86 4.0.3-5 WindowMaker 0.64.0-2 GTK+ 2.2.0 (Built from source, no errors, though w/o (optional) ftk stuff) Java SDK 1.4.1_01 fcs linux i586 (from Sun's RPM) Additional info: I tried the Motif version first (still have it in separate, re-named directory), and it did *not* have this problem. I didn't care too much for Motif look-n-feel, so I decided to try GTK+ version. Looks *much* better - more usable, IMO. Will keep using GTK+ for now, esp. since it is 'early access', I really like what I've seen so far and read in the whitepaper, etc., and you folks might appreciate the feedback? (I take my development editor very seriously, and this looks like a possible Emacs competitor. At least for Java, so far!)
I have just compiled the GTK2.2 and have experienced the exact same problem. The Eclipse with this lib is not usable. I will revert back to GTK2.0 in order to have Eclipse functional again.
Are there entries in workspace/.metadata/.log?
Thanks for the responses! Sorry, workspace/.metadata/.log doesn't even exit. I tried to create a project, using the wizard (in order to try and create a log file?) but it 'hung' after clicking 'Finish' - same symptoms. FYI - I've tried the M4 GTK build, and it doesn't seem to have this problem. I'll answer only this one e-mail - since 29002 was intended essentially as a continuation of this report. (29001). Please keep up the good work, and I will be happy to continue this if you like - but I would prefer to use the more stable builds - maybe I will revert to 2.0 as well.
Typo, sorry - should be 'workspace/.metadata/.log' doesn't even exist'.
Additional information: "I have checked the .log and there is no indication on error. The problem seem quite strange. When I launch eclipse everything seems to be working OK. But as soon as I want to save a file it hangs. The only solution is to kill eclipse. I have succesfully converted back to version 2.0.6 and it is back to functional and no error. I hope that helps. Jan"
I'm running Eclipse M4 on GTK 2.2.0, Redhat 8.0 and I can not reproduce this problem. I think redhat 7.1 is way too old to run GTK 2.2.0. note: i'm running on japanese machine... which is your locale ? en_US.UTF-8 ?
I have also experienced this bug on Gentoo linux with GTK+ 2.2.0 in Linux 2.4.19. I find no log file or anything after the hang, and it seems to hang just about everywhere. It hangs on shutdown with the exact same systems, and it hangs when attempting to perform an update. After two hangs, I think I'll just keep using jEdit.
*** Bug 29002 has been marked as a duplicate of this bug. ***
I think that 28228 is also this problem.
Chris has indicated the M4 doesn't seem to have the problem. Zed A. Shaw indicates that there are hangs in Eclipse everywhere. I believe this is true but that the hangs are not GTK 2.2 specific. Zed, I'm going to close this as WORKSFORME because I can't get GTK 2.2 to hang. If you are still hanging on GTK 2.2 and you switch to GTK 2.0.6 and the hanging goes away, this is very valuable information - please reopen this bug. Thanks.
