Job found still running after platform shutdown eclipse

Posted March 15th, 2012 in Razno by Metod

If your eclipse crashed and refuses to start, saying something along the lines of: Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown, then try the following.

$ rm -rf YOUR_PROJECT_DIR/.metadata/.plugins/org.eclipse.core.resources

Start eclipse. However, all your projects will be gone.

You can import them via File -> Import -> Existing Projects into Workspace; then select the directory where you had your projects.

EDIT: I just found a better way. (source)

$ rm YOUR_PROJECT_DIR/.metadata/.plugins/org.eclipse.core.resources/.snap

This way you do not need to reimport your projects.


As IGx89 suggested in the comments, you can also try the following:

$ rm YOUR_PROJECT_DIR/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi


62 Responses so far.

  1. Samuel Zarza says:

    Thank you very much!!
    It worked!

  2. David George says:

    Thanks a lot, that worked for me too for SpringToolSuite. Always something crapping out with Eclipse!

  3. Ben says:

    Awesome – the “better way” saved me a TON of effort 😀

  4. Aravind Badrinath says:

    Awesome. Helped a lot. Thank you!

  5. LDPX says:

    Just deleting the snap file worked for me. Thanks for pointing me in the right direction!

  6. Nirmalya Sengupta (@baatchitweet) says:

    Just when I was at my wit’s end, in trying to find out what to do! Many thanks, Metod! I wonder if anyone has ever found out how much time is saved because of such posts made by people like you!

  7. Agam Brahma says:

    Whew … thank you, thank you, THANK YOU !!

  8. Vikas says:

    I have now and then (today for example) had the secarh for references function break down on me. Starting with -clean does not help and building a new workspace (which I have done a few times as well) feels a bit too much. What I have found is that if the type related stuff start to act up, closing down Eclipse and then removing all .index files from .metadata\.plugins\org.eclipse.jdt.core give you a good chance to get back to normal when you start up Eclipse next time.

  9. Dorien says:

    Super! Thanks!

  10. Paco says:

    I couldn’t find .snap……….
    rm: cannot remove `C:/Users/FVazquez/workspace/.metadata/.plugins/org.eclipse.core.resources/.snap’: No such file or directory
    So, what I did was:
    1. to rename org.eclipse.core.resources for org.eclipse.core.resources_old.
    2. star eclipse
    3. close eclipse
    4. delete org.eclipse.core.resources
    5. rename org.eclipse.core.resources_old to org.eclipse.core.resources
    6. star eclipse

    eclipse opened and my projects are there, they build correctly from eclipse.

  11. George Hong says:

    Thank you very much, you save my android project.

  12. Seemant Shrivastava says:

    This morning suddenly I saw the error. This solution worked for me too. Thanks a lot for your post. Great help.

  13. xenover says:

    Worked fine, thanks! 🙂

  14. Mike says:

    Thanks so much!

  15. ron says:

    none of the above worked for me. i deleted (on windows) org.eclipse.core.resources and then started eclipse with -clean. eclipse complained and wouldn’t open but created a new org.eclipse.core.resources. i’m getting (in the log): !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.AbstractWorkingSetManager$9

  16. niouzes says:

    great great great !!!

    thanks a lot

    (boring all these issues when starting eclipse)

  17. Metod says:

    @ron, have you tried Paco’s solution? You should not remove that directory, just rename it temporarily.

  18. Qapp says:

    I tried both Razno and Paco’s methods. My experience was the same as Ron’s. Eclipse recreates the org.eclipse.core.resources folder after I rename the original org.eclipse.core.resources_old, but it closes near the beginning of its start and never completely loads.

  19. Metod says:

    After that did u delete the org.eclipse.core.resources and rename the org.eclipse.core.resources_old back?

  20. Qapp says:

    Yeah. Eclipse then failed to load once I tried to restart it. These issues all followed an unsuccessful attempt to send an app I built to the emulator. Eclipse gave me an error “Dex Loader] Unable to execute dex: GC overhead limit exceeded” “MY_APP_NAME] Conversion to Dalvik format failed: Unable to execute dex” From what I read on Stack Exchange this is caused by not having enough RAM on my PC to run Eclipse. I had ran it through several builds, but was never able to run the app in the emulator.

  21. AndroidDev says:

    Thanks Metod, this was incredibly useful.

    Btw I’d recommend removing or updating “Edit2” in your post

    I’m running Eclipse (Juno) on Windows 7.
    Renaming org.eclipse.core.resources to org.eclipse.core.resources.old launched Eclipse, but after I renamed it back to org.eclipse.core.resources, I ran into the same old problem.

    After that I took a second look at your post and followed your original instruction (I did del org.eclipse.core.resources\.snap)

    That fixed the problem.

    So the correct fix is to delete .snap (I’m assuming that Paco had a different problem which got fixed by the renaming trick)

  22. Metod says:

    Thanks for pointing that out. I will remove that edit. 🙂

  23. IGx89 says:

    Deleting .snap didn’t work for me (just increased the number of errors in the log), but deleting .metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi did (see http://stackoverflow.com/questions/11310970/eclipse-juno-doesnt-start/12045547#12045547)

  24. Phoenix says:

    I did the same as IGx89: deleting the workbench.xmi file solved the problem for me, but I had to reimport my projects.
    Thanks 🙂

  25. Sarah says:

    Thanks IGx89! Your solution was the only one that worked for me! Cheers

  26. Blue Pill says:

    Same as IGx89, delete workbench.xmi works for me.

  27. Felipe Gasparino says:

    Thanks for IGx89, it worked for me too… Deleting resources just caused more problems, however, I had used this solution before and worked….

    Thanks all.

  28. GreuM says:

    Thank you Razno, you saved my day !

  29. yswy says:

    I have deleted all the .snap files in my workspace, but it still doesn’t work. Any ideas?

  30. Hussain says:

    Thanks IGx89, your solution worked for me

  31. George says:

    Also guys, if you have widecap installed on your system – that might be a problem. I was using widecap and once removed, eclipse started working again.

    Here’s the bug link:


  32. Android-Developer says:

    This works like a dream! Thanks!

  33. Naveen says:

    It works for me also
    Thank you

  34. Berlin says:

    Thanks for Paco !~you save my project

  35. A says:

    I have had no luck yet in fixing this problem. Any other ideas?
    Before this occurred I had Java Heap Space and GC Overhead Exceeded out of memory errors. I am not sure if that will help…

  36. […] down eclipse the error causing task was still running. Some insight might be found here as well: http://www.metod.si/job-found-still-running-after-platform-shutdown-eclipse/ , although it was not the same […]

  37. Analista says:

    Thanks a lot, I remove the “.snap” file and works like a charm!

  38. sam says:

    removing “.snap” didn’t work for me, but removing workbench.xmi did work.. thanks..

  39. jc says:

    Thanks,the “another way” helps!

  40. […] problems could be worked-around with the –clean flag and luckily, I discovered a blog post with a workaround for the nastiest Eclipse startup […]

  41. gdou says:

    thank you very much!!!

  42. mario says:

    thank you so much, you saved a lot of time…

  43. tuiz says:

    Thanks a lot, this helped me:
    $ rm YOUR_PROJECT_DIR/.metadata/.plugins/org.eclipse.core.resources/.snap

  44. Jean says:

    I also did not find the /.snap file. I also tried to rename the org.eclipse.core.resources to _old, launched (never launched up), and deleted the newly created org.eclipse.core.resources, renamed the _old back to org.eclipse.core.resources. The way showed the same original problem.

    Then, I tried to delete the .metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi. This way works WELL. It lost the workbench layout, but everything works well.

    Thank you so much for this blog and all that who contributed for the comments.
    Time and time again, online blog helps out of these crisis.

  45. joshy8400 says:

    Thanks, .xmi removal saved me the rest of the day.

  46. Loquito D. Sikello says:

    xmi was removed, worked fine

  47. Gaurav Bhandari says:

    Cool, Worked like a charm 🙂 With the edited version my GIT repo was also saved …..