Take the 2-minute tour ×

I'm using Eclipse, and at random times, it will just freeze up and stop responding. Does this happen to anyone else? It usually happens when I click on a line of code, whether it be Java or XML. Any ideas on how to fix it?

System Specs:

enter image description here

share|improve this question
one question for clarification: do you mean it freezes and doesn't ever respond again, or is it temporary? for the latter, one thing i do is add the Progress View to the bottom of the perspectives i use most, and leave it open when i'm experiencing these kinds of lags. the system may be performing some background indexing or something that may be causing it to stop responding. –  john.k.doe Jul 24 '12 at 20:53
I've posted the specs in the original post. It freezes for about 30 seconds and then works suddenly. I've added the Progress view so I'll see if it's doing something in the background. –  Cole Jul 24 '12 at 21:14

8 Answers 8

Open your workspace\.metadata\.log file. That will tell you usually what is going wrong.

share|improve this answer
What is one to do if they don't understand any of what's in that file? No help. –  KFP Jan 24 at 18:39
@KFP Can you try pointing eclipse to a new workspace and work using it for a while? –  Ajay George Jan 25 at 1:46
@AjayGeorge, How can we find out where is the workspace folder if Eclipse wouldn't even respond? –  Pacerier Nov 12 at 2:16
Add -showlocation argument to your eclipse startup . It will show the workspace on the title bar –  Ajay George Nov 16 at 5:15
@AjayGeorge, Yuur solution doesn't work btw. The log doesn't tell you what's wrong. –  Pacerier Nov 21 at 10:14

I just restarted the adb (Android Debug Bridge) this way:

  1. adb kill-server
  2. adb start-server

and it works again!

share|improve this answer
Though this wouldn't work, it was the right idea for me. $ killall adb did the trick on Ubuntu –  RyanLeonard Sep 18 at 17:35
Eclipse engineers need to get their act together and stop hanging the UI due to long running processes. Whatever happened to responsive UI design? –  Pacerier Nov 13 at 8:59

Very likely your filesystem is out of sync with your Eclipse... Resource is out of sync with the file system. Using SVN? If you "Refresh" all of your projects in explorer, speed returns to normal.

share|improve this answer

Try this, it worked for me!

If you happen to have Eclipse not responding anymore sometimes, the reason could be that you sit on a 64bit machine where eclipse needs more memory. Be sure to have (at least) the following configurations in your eclipse.ini (I even use bigger values for the PermSizes):

share|improve this answer

Last night at 2am I closed my Eclipse (Juno) just fine. This morning I open it up and I get nothing but "Not Responding" on my 64bit Windows 7 machine.

I looked in [workspace]\.metadata\.log and it showed an error with Invalid property category path: ValidationPropertiesPage

I cuss it out pretty good and then show it who's the boss :

  1. delete [workspace]\.metadata folder
  2. delete [workspace]\[project]\.settings
  3. Open up Eclipse to the same workspace as before, re-import your project.

Which brings me to another topic... Eclipse -> import -> Android -> Existing Android code into workspace... seems to be broken once again. But that's a different topic.

share|improve this answer

If there is a project you earlier imported externally (outside of Workspace), that may cause this problem. If you can access Eclipse try to remove it. If you are getting the 'No responding at startup', then go delete the file at source.

This will solve the problem.

share|improve this answer

I had a problem like you. But I am Windows 8.1 64 bit user. At first I use eclipse Kepler on my 8.1. The eclipse often become not responding when I worked on. After that, I decide to back to eclipse Juno and it works fine now.

share|improve this answer

for me, it was because of all the outgoing files, i.e workspace is not in sync with SVN, due to the 'target' folders (maven project, or when building web project), add them to svn:ignore.

share|improve this answer

Your Answer


