score:8

Accepted answer

you may want to take a look at how to report a deadlock. you may also want to check the error view and/or the error log ([workspace]/.metadata/.log). if that doesn't help, you'll probably need to include more info about which plugins you have installed and which projects you have. can you create a minimal workspace which reproduces the problem?

score:0

i just had the same problem.

by using task manager to kill the build process and exiting eclipse with no projects open, i was able to get back into eclipse and clean the project without opening it. i then restarted eclipse again,loaded my project and all ok.

score:0

i've found that this might also happen if you rebuild a workspace with a project containing a lot of image data (such as a dedicated images project). might be best to put something like that into its own workspace and handle it separately to the rest of the projects you deal with.

if you can't, then don't clean that project when you clean and rebuild. only rebuild when necessary.

score:0

in my case problem arise after importing downloaded project - stuck at 80% build. solved by adding write permissions for group to project's files (ubuntu 12.04).

score:0

in my case it helped to remove the source folders from my favorites in the windows explorer (windows 8.0). it seems that the build was not actually stuck, but triggered in some kind of infinite loop (as mentioned here - bug 342931).

score:0

sometimes the problem seems to be fixed by killing other programs which have files open from the project folder.

score:0

looking at the logs in [workspace]/.metadata/.log provided useful information for me. turned out there was a java.lang.outofmemoryerror: permgen space error when the workspace build would hang. this can be edited in the eclipse.ini or sts.ini(if you are using springsource tool suite) file.

score:0

i faced the same problem when i tried to install angular.js with bower in my project. i seems bower has lots of javascript files it downloaded automatically which caused my ide to stuck in validation process for a long time. so, i solved this problem this way,

  • i first installed tern.js 0.9.0.
  • then i went to the project properties, selected tern script path included only the path i needed for validation, my project's javascript folder. i excluded other path like placeholders, angular.js files, jquery files.
  • i selected the javascript from the properties again and did the same things in include path's source.

my ide currently working without freezing. i took help from there. tern i guess it can be helpful, where any ide stuck due to lots of javascript file.

score:0

i tried lots of these suggestions, but the only thing that finally worked for me was creating a new workspace, and freshly checking out all my projects into that folder. then it worked fine ;-)

score:0

i just restarted eclipse and it started working the next time.

score:0

refresh all the projects u want to build. worked

score:0

restart eclipse.
it worked for me several times.

score:0

i was able to solve this by removing extra folder that eclipse had created in my eclipse installation folder. i didn't install and i was using eclilpse neon 3 with spring tool suite also installed. but, when i looked into extracted eclipse installation, i had c: folder which had some folder structure. it was mirror image of my downloads folder. i removed it and restarted.

it worked for me!

score:0

none of the the answers here worked for me. what worked was to delete the following folder

c:\users\your username\workspace\project name.metadata.plugins\org.eclipse.core.resources.projects\project name\.indexes

score:0

rather than debug and find the exact root cause(s) for this, i just deleted the projects and the metadata folder. eclipse will rebuild the .metadata file the next time it's launched.

i then pulled in the latest project code and the problem was solved. it was more work as i had to reconfigure everything, including my servers, but build workspace had been stopping at 50% for anywhere from 3 to 5 minutes before it would completely finish, so it was worth the effort.

also, i've found that with eclipse, if you stop the build workspace before it completes and shut down eclipse if that hangs up everything, you can really mess up your configuration and waste lots of time trying to get it stable again. i'm using eclipse oxygen, but i've had this happen in all the versions of eclipse i've used, so i really try to avoid it, if possible.

score:0

inside the project folder open .project file. there is a bad entry and it might help

    <buildcommand>
        <name>org.eclipse.m2e.core.maven2builder</name>
        <arguments>
        </arguments>
    </buildcommand>

score:0

if you are using maven as a build tool you might want to:

  1. close eclipse

  2. delete dependency directories located in .m2/repository/ - in linux it's located under home directory and in windows it should be in c:\users<yourusername>.m2 (replace '' with your username)

  3. start eclipse and enjoy normal work :)

that helped me resolve this issue and i hope it helps you too. :)
cheers!

p.s. i've edited my answer (as @howlger asked) where it was also suggested to delete .eclipse and .p2 folders as it can do harm (although it did not in my case + i had to reinstall some of plugins i'm using).

score:0

in case there is a problem on start when building your project disable the build automatically from menu. project -> build automatically. this solved my problem while more sophisticated solutions could not.

score:0

this can also happen if you have an empty java file that is named and classpath-located exactly like another java file (which can happen when resolving merge conflicts for moved resources).


for example, the following setup causes this issue in a multi-maven module:

  • module1/src/main/java/com/package/myclass.java (empty)
  • module2/src/main/java/com/package/myclass.java (actual valid class)

to fix, simply delete the empty java file.

score:1

unselect automatic build using eclipse-> windows->preferences helps fixing this issue.

score:1

deleting some of the jdt indexes (in .metadata.plugins\org.eclipse.jdt.core), particularly the big files, often fix or ease the problem for me.

score:2

i had same issue with my eclipse and as a solution, i created new project, copied all resources manually (using windows copy/paste) to new project, deleted old project and that's it.

sometimes, this happens due to improper system shutdown and eclipse workspace started facing similar issues.

hope it will work.

score:6

i faced similar issue in eclipse indigo. i changed the heapsize it started working correctly. i just added following eclipse.ini file -vmargs -xms1024m -xmx1024m

it worked fine after increasing the vm size

score:6

the only solution for me (luna 4.4.1) was this:

go to project properties > builders and then uncheck the javascript validator.

score:8

i have this problem whe i have too much maven projects open at once. what i tend to do is:

  • restart eclipse (sometimes i need to kill eclipse)
  • disable automatic build immediatly (project > uncheck build automatically)
  • right click the project(s) i want to have rebuild
  • close unrelated projects
  • re-enable automatic build

this enables a functioning rebuild in 99% off the cases in my workspace.

score:10

the accepted answer allowed me to get eclipse started again, but it seems that the projects lost their metadata. (e.g., all the git/gradle/spring icons disappeared from the project names.) i have a lot of projects in there, and i didn't want to have to import them all over again.

so here's what worked for me under kepler. ymmv but i wanted to record this just in case it helps somebody.

step 1. temporarily move the .projects file out of the way:

$ cd .metadata/.plugins/org.eclipse.core.resources
$ mv .projects .projects.bak

step 2. then start eclipse. the metadata will be missing, but at least eclipse starts without getting stuck.

step 3. close eclipse.

step 4. revert the .projects.bak file to its original name:

$ mv .projects.bak .projects

step 5. restart eclipse. it may build some stuff, but this time it should get through. (at least it did for me.)

score:10

step1:

open project directory and edit .project file, remove following lines to disable java script validation.

  <buildcommand>
      <name>org.eclipse.wst.jsdt.core.javascriptvalidator</name>
      <arguments>
      </arguments>
    </buildcommand>

save file.

step 2:

go to eclipse installed directory and open eclipse.ini(or sts.in if you have sts), change xms and xmx value based on your ram size of your computer.

-xms512m
-xmx1024m
-xx:maxpermsize=256m

or: in windows, go to eclipse shortcut in desktop, right click->properties-> add following: c:\software\eclipse\sts-3.6.2.release\sts.exe -clean -xms512m -xmx1024m

run eclipse.

go to eclipse->windows->preference->validation, enable suspend all validators. do this if you don't want do any validation listed in the list given in validator panel.

score:15

eclipse often freezes for me at 44% if i'm debugging android over usb. when disconnecting the device, eclipse starts.

score:24

eclipse -clean did not work but following did

eclipse -clean -clearpersistedstate

score:27

some time it's very helpful to execute eclipse from command line with "-clean" parameter to enforce it produce clean up for workspace.

score:149

i was able to fix this with the following:

first, exit eclipse. then temporarily move the following .projects folder to a safe location:

mv .metadata\.plugins\org.eclipse.core.resources\.projects projects

start and exit eclipse, then move the .projects folder back to where it was originally:

mv projects .metadata\.plugins\org.eclipse.core.resources\.projects

use at your own risk, of course.


Related Query

More Query from same tag