Community
Participate
Working Groups
Build Identifier: 20100617-1415 Using Eclipse IDE for Java Developers (build id 20100617-1415) on Vista 64-bit with all 64-bit installs. It hangs / locks up quickly and easily. Haven't noticed any particular trigger -- can be when editing, when switching to files, pretty much anything. Turned off UDC, didn't help. I can't get any work done. Reproducible: Always
Please attach a thread dump. http://wiki.eclipse.org/How_to_report_a_deadlock Does it hang with Eclipse Classic? http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/index.php
Created attachment 174111 [details] Thread Dump when IDE locks up
Are you sure it's a hang and not an OOME (PermGen space)? There's a problem with latest Java 1.6.0_21 from Oracle, see bug 319514.
(In reply to comment #3) > Are you sure it's a hang and not an OOME (PermGen space)? There's a problem > with latest Java 1.6.0_21 from Oracle, see bug 319514. Running out of PermGen space can cause infinite loops in Equinox (don't have the bug number but I have seen it.) I expect it can also cause hangs as well.
This is what my INI already was: -startup plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.0.v20100503 -product org.eclipse.epp.package.java.product --launcher.defaultAction openFile --launcher.XXMaxPermSize 256M -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vmargs -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx384m
Randy, can you confirm whether you are using HotSpot 6u21?
I don't know if it was HotSpot or not, but it was 6u21. So, I removed everything but SDK 1.5. Set up for 2.1r1. Made simple project. Went to res -> layout -> main.xlm ... and it just spins and spins (not responding). Dang, I've never seen a development environment this unfriendly. Talking back to Apple II and TRS-80 days (Sinclair, too). Maybe it's just a perfect storm I / we stumbled into.
Randy, please either try Java 6u20 or set the VM arguments on the command line using -vmargs <vm arguments>.
My earlier comment was unfair -- I was just frustrated. I'll try the new suggestion in a few hours or ASAP.
Even easier to try: Add the following line after "-vmargs" to your eclipse.ini: -XX:MaxPermSize=256m
Yes, that makes it usable. Thanks!
*** This bug has been marked as a duplicate of bug 319514 ***