I think I might be seeing the same issue. Eclipse doesn't crash, but becomes unresponsive so that I have to kill it. Eclipse's javaw.exe takes 33% CPU on my 3 core machine (i.e. 100% of one core).
Here's my setup: Eclipse Helios (3.6) 64-Bit Sun JVM 6u20 (1.6.0_20) ADT 0.9.7.v201005071157-36220 Windows 7 64-bit For me, it started when I upgraded to Eclipse 3.6 and a 64-bit JVM. Immediately after the upgrade it seemed like Eclipse was very sluggish and unstable, so I ended up increasing the memory available to it by starting with: C:\eclipse\eclipse.exe -vmargs -Xmx1536m -XX:MaxPermSize=128m It looks like my problem is caused by running out of PermGen space. Unfortunately it was a bit hard to figure that out. To start, I launched Eclipse with a java console by using java.exe instead of javaw.exe: C:\eclipse\eclipse.exe -vm "C:\Program Files\Java\jdk1.6.0_20\bin \java.exe" -vmargs -Xmx1536m -XX:MaxPermSize=128m With the console, I can see that an OutOfMemoryError is being thrown due to PermGen space. Then Eclipse becomes unresponsive. I just increased the PermGen space so I should know soon if that fixes my issue. Hope that's somehow helpful. If we're not seeing the same issue, maybe the above might help diagnose it? VisualVM was also helpful to me to watch the PermGen space (see JDK_HOME\bin \jvisualvm.exe). On Jul 26, 1:02 pm, Frank Weiss <[email protected]> wrote: > Some more specifics in the OP would have saved me the trouble of asking: > > eclipse version? > system memory size? > at startup of eclipse? > using the graphical layout editor? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
