51

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

Kara
  • 6,115
  • 16
  • 50
  • 57
Cole
  • 2,805
  • 9
  • 44
  • 61
  • 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
  • Yes, I think there is a tendency for GUI freezes (which do not recover) if trying several things at once if it is responding slowly for whatever reason (not memory in my case). For instance, I tried closing a project and then while it was starting that off, I tried opening a pom in a different project. Boom! I get the feeling the GUI doesn't handle multiple tasks very well. After this, getting it and maven to compile a large number of projects and getting back to the starting point may approach half an hour, unfortunately.. – nsandersen Aug 03 '18 at 08:57

11 Answers11

41

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

R. Oosterholt
  • 7,720
  • 2
  • 53
  • 77
Ajay George
  • 11,759
  • 1
  • 40
  • 48
  • 1
    @KFP Can you try pointing eclipse to a new workspace and work using it for a while? – Ajay George Jan 25 '14 at 01:46
  • @AjayGeorge, How can we find out where is the `workspace` folder if Eclipse wouldn't even respond? – Pacerier Nov 12 '14 at 02:16
  • Add `-showlocation` argument to your eclipse startup . It will show the workspace on the title bar – Ajay George Nov 16 '14 at 05:15
  • 6
    @AjayGeorge, Yuur solution doesn't work btw. The log doesn't tell you what's wrong. – Pacerier Nov 21 '14 at 10:14
  • @AjayGeorge - Your suggestion of opening in a new workspace just worked for me. I did this: 1. Shut down Eclipse, which was (Not Responding). 2. Reopened using another workspace. 3. Shut it down again. 4. Reopened in the original workspace. – linnse Feb 24 '21 at 13:48
30

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):

-Xms512m
-Xmx1024m
-XX:PermSize=64m
-XX:MaxPermSize=128m
Sumit Singh
  • 15,743
  • 6
  • 59
  • 89
LoveProgramming
  • 321
  • 3
  • 4
  • 1
    Worked nicely. Thank you. Btw, I didn't have permisize or maxpermsize intially. What are these for? – eaglei22 Mar 10 '15 at 17:03
  • 1
    How about similar settings for Java 8? (These do not exist anymore in Java 8.) – Frederic Leitenberger Apr 12 '17 at 14:22
  • 1
    afaik they should be -ms and -mx now, in fact these have existed previously, the X-ones have been deprecated for a while – xeruf Oct 27 '17 at 14:30
  • wow I can't believe it was this simple. You'd think a 64 bit .zip/installer would have this setting by default – Fueled By Coffee Mar 17 '18 at 00:33
  • Since, Java 8 PermGen support has been disabled, instead MetaSpace is used. Instead of PermSize, use, ```-XX:MetaspaceSize=128M``` and ```-XX:MaxMetaspaceSize=256M``` – Dusayanta Prasad Jan 29 '22 at 18:42
  • Thanks for your advice but this does not help - as soon as I click on any source code in eclipse it crashes. This only happened since last week, was working fine for a year or so on a very large project before that. – Gregory Fenn Jun 21 '23 at 08:18
15

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

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

and it works again!

eeadev
  • 3,662
  • 8
  • 47
  • 100
10

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.

Someone Somewhere
  • 23,475
  • 11
  • 118
  • 166
  • +1 I think over time my projects were upgraded to different versions of Eclipse which shows in my logs. I like the fresh start approach. – hram908 Jun 17 '19 at 15:41
2

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.

Ryan Donovan
  • 21
  • 1
  • As an addition, my problem was while trying to sync with repository Eclipse would always hang. Project -> Clean fixed the issue for me. – whla Aug 29 '19 at 22:39
2

I had similar symptoms recently. Turned out it was caused by the Subversion server being unavailable - once that was restarted I was able to right-click. My environment was Eclipse Luna with Subclipse.

So worth checking that any connected source control systems are operational. Hope that helps.

m_at_vidavia
  • 41
  • 1
1

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.

mel3kings
  • 8,857
  • 3
  • 60
  • 68
1

I kept running into this problem every time I tried opening eclipse. I resolved it by unplugging my android device's USB from my laptop, and eclipse worked again.

Kacy
  • 3,330
  • 4
  • 29
  • 57
0

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.

Umit Kaya
  • 5,771
  • 3
  • 38
  • 52
0

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.

Luki B. Subekti
  • 822
  • 10
  • 9
-5

This may help

In your eclipse,

1) Go to Help

2) Click Eclipse marketplace

3) search - optimizer

install "optimizer for eclipse"

enter image description here

Parth Pithadia
  • 276
  • 1
  • 3
  • 18
  • 10
    Run away. That optimzer requires an email and user name, and it broke my Eclipse config. Now Kepler won't even start because the memory settings prevent the creation of the JVM. I had it all working... then I "fixed" it with this non-optimizer. Now I have to "unoptimize" the configuration to get it working again. Flame suit on. – J Slick Jul 09 '15 at 15:35