Eclipse Community Forums: Technology Project and PMC

Help

Home

Home » Eclipse Projects » Technology Project and PMC » Eclipse Freezing Up

Show: Today's Messages :: Show Polls :: Message Navigator

Eclipse Freezing Up [message #57858]

Mon, 15 September 2003 23:57

Eclipse User

Originally posted by: KobyBoy.yahoo.com

Hello All,

I've been a satisfied Eclipse user now for the past year but suddenly the day
before yesterday Eclipse started to act up for me. Before I tell you the
symptoms I have to say that *nothing* has changed in my setup (same OS, same
JVM, same Plug-ins, etc...). I was using Eclipse 2.1 when this problem started
happening. When I fire up Eclipse everything loads fine, the GUI, my last
project I've worked on, etc... The problem is when I try to type nothing is
showing up on screen, when I try to rebuild my project I get a dialog box with
the words "Operation in Progress" and then nothing. The CPU usage jumps to
100% (50% being eaten up by X and 50% being eaten up by Java). The only way to
get rid of Eclipse is to kill the process either from the command line or with
"xkill". I'm using Gentoo Linux with Sun's 1.4.1_2 JVM and my machine has
512MB of RAM. I've downloaded the M3 build of eclipse and I get the same
problem but with this build the progress meter tells me that I have an
operation in progress. That operation is an "update for decoration". Has
anyone else been experiencing this ? Any help would be much appreciated.

Thanks in advance:

-Koby

Report message to a moderator

Re: Eclipse Freezing Up [message #57908 is a reply to message #57858]

Tue, 16 September 2003 08:20

Eclipse User

Originally posted by: daniel.megert.gmx.net

Koby Boy wrote:

> Hello All,
>
> I've been a satisfied Eclipse user now for the past year but
> suddenly the day before yesterday Eclipse started to act up for me.
> Before I tell you the symptoms I have to say that *nothing* has
> changed in my setup (same OS, same JVM, same Plug-ins, etc...). I was
> using Eclipse 2.1 when this problem started happening. When I fire up
> Eclipse everything loads fine, the GUI, my last project I've worked
> on, etc... The problem is when I try to type nothing is showing up on
> screen, when I try to rebuild my project I get a dialog box with the
> words "Operation in Progress" and then nothing. The CPU usage jumps
> to 100% (50% being eaten up by X and 50% being eaten up by Java). The
> only way to get rid of Eclipse is to kill the process either from the
> command line or with "xkill". I'm using Gentoo Linux with Sun's
> 1.4.1_2 JVM and my machine has 512MB of RAM. I've downloaded the M3
> build of eclipse and I get the same problem but with this build the
> progress meter tells me that I have an operation in progress. That
> operation is an "update for decoration". Has anyone else been
> experiencing this ? Any help would be much appreciated.
>
> Thanks in advance:
>
> -Koby
>
I suggest to start Eclipse in a console and then press Ctrl+Break
(assuming WinX client) to get a stack dump. Then file a bug report
describing the problem and attach the stack dump.

Hint: Disable the decorators (Window > Preferences > Workbench > Label
Decorations) and test whether this fixes the problem.

HTH
Dani

Report message to a moderator

Re: Eclipse Freezing Up [message #57931 is a reply to message #57858]

Tue, 16 September 2003 12:02

jelda

Messages: 42
Registered: July 2009

Member

me either facing the same problems..

that too from the last 1-2 weeks..
NO CHANGES ..
USING THE SAME 2.1 verison..
whats happening actually..
Any unwanted things happening on background??

Jelda
"Koby Boy" <KobyBoy@yahoo.com> schrieb im Newsbeitrag
news:bk5jj8$2vr$1@eclipse.org...
> Hello All,
>
> I've been a satisfied Eclipse user now for the past year but suddenly the
day
> before yesterday Eclipse started to act up for me. Before I tell you the
> symptoms I have to say that *nothing* has changed in my setup (same OS,
same
> JVM, same Plug-ins, etc...). I was using Eclipse 2.1 when this problem
started
> happening. When I fire up Eclipse everything loads fine, the GUI, my last
> project I've worked on, etc... The problem is when I try to type nothing
is
> showing up on screen, when I try to rebuild my project I get a dialog box
with
> the words "Operation in Progress" and then nothing. The CPU usage jumps
to
> 100% (50% being eaten up by X and 50% being eaten up by Java). The only
way to
> get rid of Eclipse is to kill the process either from the command line or
with
> "xkill". I'm using Gentoo Linux with Sun's 1.4.1_2 JVM and my machine has
> 512MB of RAM. I've downloaded the M3 build of eclipse and I get the same
> problem but with this build the progress meter tells me that I have an
> operation in progress. That operation is an "update for decoration". Has
> anyone else been experiencing this ? Any help would be much appreciated.
>
> Thanks in advance:
>
> -Koby
>

Report message to a moderator

Re: Eclipse Freezing Up [message #57952 is a reply to message #57908]

Tue, 16 September 2003 13:07

Eclipse User

Originally posted by: KobyBoy.yahoo.com

Daniel Megert wrote:

> I suggest to start Eclipse in a console and then press Ctrl+Break
> (assuming WinX client) to get a stack dump. Then file a bug report
> describing the problem and attach the stack dump.

I'm having this problem under Linux. Anyway I could do this under this platform ?

> Hint: Disable the decorators (Window > Preferences > Workbench > Label
> Decorations) and test whether this fixes the problem.

No can do. I can bring up the preferences window but when I click on Label
Decorations Eclipse goes nuts again by freezing the GUI and the CPU consumtion
jumps to 100%. Is there a way to load the default settings from the command
line ?

-Koby

Report message to a moderator

Re: Eclipse Freezing Up [message #57976 is a reply to message #57952]

Tue, 16 September 2003 13:56

Eclipse User

Originally posted by: daniel.megert.gmx.net

Koby Boy wrote:

> Daniel Megert wrote:
>
>> I suggest to start Eclipse in a console and then press Ctrl+Break
>> (assuming WinX client) to get a stack dump. Then file a bug report
>> describing the problem and attach the stack dump.
>
>
> I'm having this problem under Linux. Anyway I could do this under
> this platform ?

Sending kill -3 or kill -6 to the process should work. Maybe it's
another number on your system.

Dani

Report message to a moderator