When I got to work today, I brought up eclipse in my VM and it came up nicely in the synchronization view (where I had shut it down on Friday). Check for updates, and nothing was found, so … switch to the Java perspective to crank on some code when … yes, you guessed it … Eclipse locks up. I see the redraw of the perspective start, but it only draws part way. Check CPU utilization and … nothing being consumed. Eclipse has just gone into lah-lah land.
I tried all kinds of solutions, like using -clean on the startup, looking at the logs (nothing logged about the lock up). It wasn’t until I stumbled across this post that I found a solution.
Shut down eclipse and then navigate to <eclipse workspace>/.metadata/.plugins/org.eclipse.core.resources and remove the .snap file.
That’s all I had to do; the post I found indicates that in extreme cases, you may have to remove the entire .plugins directory — but fortunately, I didn’t have to. So, my projects, plugins, settings, etc., were all left intact.
Hope this helps somebody; I only lost 2 1/2 hours of work because of it … 8^)
— A bit of an update to this one; periodically, I still end up in this state. Today, however, the fix we detailed didn’t work at all. In my particular case, this seems to happen when Eclipse starts up in something other than the Java perspective, and the “Not Responding” state begins when switching to that perspective. This latest time, what seemed to do the trick was to start up in the synchronization view (the view I had been coming up); then open the project explorer and close all the projects. Only after the projects are closed should you try to switch to the java perspective. Once I did that, I was able to operate normally … so far …
— and one tiny update, really just adding another data point. Eclipse was locking up on my again (“Not Responding”). I used the “project explorer & close all projects” technique described above, and I got right back in. A few weeks ago, when this happened, I noticed a log message (after having updated my jvm) about a lock timout. A little digging indicates there may be a deadlock issue in some part of eclipse … ?