Community
Participate
Working Groups
Just upgraded to 3.0 release Eclipse/JDT. Once or twice a day, during random edits of either code or Javadoc, javaw.exe kicks in (perhaps for syntax completion/checking) consumes 95% of CPU, and hangs the Eclipse IDE. Ultimately the process must be killed. Tried both the IBM 1.4.1 and 1.4.2 JDKs for Windows, with same results. Others in org experiencing same problem. -- Todd
We need at least some information to reproduce the problem. Could you please run in debug mode and when the hang occurs, use Ctrl + Break in the java console and attach the thread dumps. Thanks.
Created attachment 14132 [details] Java dump during 98% CPU usage of Eclipse 3.0 session
Trace indicates that the time is spent in the editor. Moving to JDT Text for comments.
To me this looks like you reach the VM's (or your machines) memory limit. You wrote "and hangs the Eclipse IDE" but when looking at the dump the editor is seems still working and not hanging in a dead-locked. - how long did you wait before killing Eclipse? Next time when it happens, please create thread dumps at let's say a 30 seconds intervals and attach them - how much memory do you give Eclipse? - next time when it happens check the VM size in the Windows Task Manager Reopen once this information has been provided.
> how long did you wait before killing Eclipse? Next time when it happens, >please create thread dumps at let's say a 30 seconds intervals and attach them Typically wait 5-10 mins. Will create more dumps on next hang. > how much memory do you give Eclipse? According to doc, the default is 64MB. I'm now starting Eclipse with - Xmx512M. Machine swap space is 4Gig. > next time when it happens check the VM size in the Windows Task Manager Assuming I can open Task Manager. Typically, I cannot. If the JVM is running out of VM memory, shouldn't the Eclipse app signal same?
>I'm now starting Eclipse with -Xmx512M I assume you use -vmargs -Xmx512M correct? >Machine swap space is 4Gig. Swap space can actually cause the pain: the time can well be spent swapping Eclipse back in e.g. if you switched to another app, minimized Eclipse or simply didn't do anything. WindowsXP likes to swap out stuff even if there's still tons of RAM. >If the JVM is running out of VM memory, shouldn't the Eclipse app signal same? It will but it can take quite some time because it tries to garbage collect first >Assuming I can open Task Manager. Typically, I cannot. Open it before and give it a higher priority Please reopen once you can check the VM memory and attach it here together with the dumps.
Get rid of deprecated state.
.
