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

score: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.

score: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.

score: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.

score: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.

score: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.

score: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.

score: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.

score:15

i just restarted the adb (android debug bridge) this way:

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

and it works again!

score:29

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

score:41

open your workspace\.metadata\.log file. that will tell you usually what is going wrong.


Related Query

More Query from same tag