How do I prevent Eclipse from hanging on startup

Question

I am using Eclipse 3 3   Europa    Periodically  Eclipse takes an inordinately long time  perhaps forever  to start up  The only thing I can see in the Eclipse log is         ENTRY org eclipse core resources 2 10035 2008-10-16 09 47 34 801      MESSAGE The workspace exited with unsaved changes in the previous session  refreshing workspace to recover changes    Googling reveals someone s suggestion that I remove the folder   workspace  metadata  plugins org eclipse core resources  root  indexes   This does not appear to have helped   Short of starting with a new workspace  something which I am not keen to do  as it takes me hours to set up all my projects again properly   is there a way to make Eclipse start up properly

User · Answer

Also look at http   www lazylab org 197 eclipse eclipse-hanging-on-startup-repair-corrupt-workspace   99  Recommended Solution works      i e  Removing  snap file  But if it did not worked then we have to try to remove indexes folder and further workbench folder

User · Answer

I had no snap files   Going through the help menu installation list  at least 90  of my plugins had the uninstall button deactivated so I could not handle it through there   Under startup shutdown most of plugins were not listed   Instead  I had to manually remove items from my plugins folder   Wow  the startup time is much faster for me now  So if everything else does not work and you have plugins that are disposable  this could be the ultimate solution to use

User · Answer

I used eclipse -clean -clearPersistedState and that worked for me    Warning  This may remove all projects from the workspace

User · Answer

Since I don t have a  snao or  prefs file in  metadata plugins org eclipse core resources folder  running on OS X   what did the trick for me was copy the  project folder to old project  start Eclipse  and check      Windows -  Preferences -  General -    Startup and Shutdown -  Refresh   workspace on startup   as proposed by matt b  After that  I closed Eclipse  renamed the folder old projects back to  projects and after that everything worked fine again

User · Answer

I used eclipse -clean -clearPersistedState and that worked for me    Warning  This may remove all projects from the workspace

User · Answer

my solution is to remove this dir   workspace  metadata  plugins org eclipse e4 workbench   what is did was first remove  move it to a save place  all from  metadata  eclipse started all new  all my settings gone   then i added bit by bit back into the  metadata dir until it dit not work again  this way i found i only had to remove this dir  And now Eclipse started with all my settings still in place   it seems that in the file in this dir the windows which should be opened on startup are listed and some how it could not find one off them so it hung  why i m unclear because the file which in complained about in the logging was on my filesystem

User · Answer

What worked for me was this-- On Ubuntu   Ctrl F1 ps -e kill -9 for process ids of eclipse  java and adb

User · Answer

You can try to start Eclipse first with the -clean option   On Windows you can add the -clean option to your shortcut for eclipse  On Linux you can simply add it when starting Eclipse from the command line

User · Answer

You can try to start Eclipse first with the -clean option   On Windows you can add the -clean option to your shortcut for eclipse  On Linux you can simply add it when starting Eclipse from the command line

User · Answer

I tried all of the answers in this thread  and none of them worked for me -- not the snap files  not moving the projects  none of them    What did work  oddly  was moving all projects and the  metadata folder somewhere else  starting Eclipse  closing it  and then moving them all back

User · Answer

This may not be an exact solution for your issue  but in my case  I tracked the files that Eclipse was polling against with SysInternals Procmon  and found that Eclipse was constantly polling a fairly large snapshot file for one of my projects   Removed that  and everything started up fine  albeit with the workspace in the state it was at the previous launch    The file removed was    lt workspace gt   metadata  plugins org eclipse core resources  projects  lt project gt   markers snap

User · Answer

I had a similar problem after I updated eclipse on Mavericks  Eventually I found that in the eclipse plugins directory the com google gdt eclipse login jar had version numbers at the end  I removed the version number from the name and it all started fine

User · Answer

Check that the Workspace Launcher hasn t opened on your TV or some other second monitor  It happened to me  The symptoms look the same as the problem described

User · Answer

UFT causing issues with RDz  Eclipse based  after install These suggestions will allow to work around this situation even with the environment variables in place and with corresponding values    Note  Conflicting application will not be recognized in a java context because it is being excluded from the java support mechanism    Impact  Excludes Add-ins support from hooking to conflicting application executable via Windows Registry Editor Requirement  The application must be started by an EXE file  except Java exe Javaw exe jpnlauncher exe   Instructions   a  Locate the executable filename of the application conflicting with add-in s  support  Either use the Task Manager or the Microsoft Process Explorer    b  Open Windows Registry Editor    c  Navigate to  HKEY LOCAL MACHINE SOFTWARE Mercury Interactive JavaAgent Modules For 32bits applications on Windows x64  HKEY LOCAL MACHINE SOFTWARE Wow6432Node Mercury Interactive JavaAgent Modules  d  Create a DWORD value with the name of the conflicting software executable filenmae and set the value to 0

User · Answer

Windows -  Preferences -  General -  Startup and Shutdown   Is Refresh workspace on startup checked

User · Answer

no need to delete entire metadata file  just try deleting the  snap file from org eclipse core resources on your workspace folder  ex  E  workspaceFolder  metadata  plugins org eclipse core resources

User · Answer

I had a similar problem with a rather large workspace in 3 5 and no  snap-files anywhere to be seen   Windows -  Preferences -  General -  Startup and Shutdown -  Refresh workspace on startup  seems to be a workspace-related setting and so I couldn t change it for the workspace that was causing the hang   Running eclipse with the command line parameter -refresh and then changing the setting seems to do the trick

User · Answer

JAVA VERSION COULD BE PROBLEM   I tried few answers given above  But it didnot work  But meanwhile I was trying them it clicked to me that I switched the java version for some other stuff  amp  forgot to switch back  Once I jumped back to the previous version  Eclipse started working for me

User · Answer

I did this    cd to  metadata plugins org eclipse core resources remove the file  snap Noticed the Progress tab was doing something every few seconds  it seemed stuck Exit eclipse  DO NOT FILE RESTART HERE OR YOU HAVE TO GO BACK TO STEP 1 AGAIN  Open eclipse again    Using -refresh or -clean when starting eclipse did not help

User · Answer

This may not be an exact solution for your issue  but in my case  I tracked the files that Eclipse was polling against with SysInternals Procmon  and found that Eclipse was constantly polling a fairly large snapshot file for one of my projects   Removed that  and everything started up fine  albeit with the workspace in the state it was at the previous launch    The file removed was    lt workspace gt   metadata  plugins org eclipse core resources  projects  lt project gt   markers snap

User · Answer

Check that the Workspace Launcher hasn t opened on your TV or some other second monitor  It happened to me  The symptoms look the same as the problem described

User · Answer

try        cd to  lt workspace gt   metadata  plugins org eclipse core resources     remove the file   snap  or  markers in Indigo

User · Answer

Watch out for zero-byte  plugin files in the  WORKSPACE-DIR   metadata  plugins folder  I just deleted one in there and it fixed my freezing issues

User · Answer

The freezing   deadlock can also be caused by this bug on GTK3   Xorg https   bugs eclipse org bugs show bug cgi id 568859 Can be workarounded by using Wayland session  although in my case Eclipse fails to detect reasonable font for some reason and looks like this   Related  https   www reddit com r swaywm comments bkzeo7 font rendering really bad and rough in gtk3  https   www reddit com r swaywm comments kmd3d1 webkit gtk font rendering on wayland

User · Answer

Unfortunately  none of these solutions worked for me   I ended up having to create a new workspace  then imported the existing projects into the new workspace   Unfortunately  you lose your preferences when doing so  so  remember to export your settings anytime you change them

User · Answer

I had a very similar problem with eclipse  Juno  on Fedora 18   In the middle of debugging an Android session  eclipse ended the debug session    I attempted to restart eclipse but it kept haning at the splash screen   I tried the various suggestions above with no success    Finally  I checked the adb service  android debug bridge        adb devices List of devices attached  XXXXXX offline   I know the android device was still connected but it reported it offline    I disconnected the device and shut down the adb service     adb kill-server   Then I waited a few seconds and re-started the adb service     adb start-server   And plugged my android back in   After that  eclipse started up just fine

User · Answer

I had a very similar problem with eclipse  Juno  on Fedora 18   In the middle of debugging an Android session  eclipse ended the debug session    I attempted to restart eclipse but it kept haning at the splash screen   I tried the various suggestions above with no success    Finally  I checked the adb service  android debug bridge        adb devices List of devices attached  XXXXXX offline   I know the android device was still connected but it reported it offline    I disconnected the device and shut down the adb service     adb kill-server   Then I waited a few seconds and re-started the adb service     adb start-server   And plugged my android back in   After that  eclipse started up just fine

User · Answer

Windows -  Preferences -  General -  Startup and Shutdown   Is Refresh workspace on startup checked

User · Answer

This may help  In your eclipse   1  Go to Help  2  Click Eclipse marketplace  3  search - optimizer  install  optimizer for eclipse

User · Answer

Watch out for zero-byte  plugin files in the  WORKSPACE-DIR   metadata  plugins folder  I just deleted one in there and it fixed my freezing issues

User · Answer

Well  I had similar behaviour while starting eclipse over X11  I forgot to tick the enable X11 forwarding in my putty

User · Answer

I had a similar problem after I updated eclipse on Mavericks  Eventually I found that in the eclipse plugins directory the com google gdt eclipse login jar had version numbers at the end  I removed the version number from the name and it all started fine

User · Answer

Unfortunately  none of these solutions worked for me   I ended up having to create a new workspace  then imported the existing projects into the new workspace   Unfortunately  you lose your preferences when doing so  so  remember to export your settings anytime you change them

User · Answer

On Mac OS X  you start Eclipse by double clicking the Eclipse application  If you need to pass arguments to Eclipse  you ll have to edit the eclipse ini file inside the Eclipse application bundle  select the Eclipse application bundle icon while holding down the Control Key  This will present you with a popup menu  Select  Show Package Contents  in the popup menu  Locate eclipse ini file in the Contents MacOS sub-folder and open it with your favorite text editor to edit the command line options   add   -clean  and  -refresh  to the beginning of the file  for example   -clean -refresh -startup          plugins org eclipse equinox launcher 1 3 0 v20130327-1440 jar --launcher library

User · Answer

I did this    cd to  metadata plugins org eclipse core resources remove the file  snap Noticed the Progress tab was doing something every few seconds  it seemed stuck Exit eclipse  DO NOT FILE RESTART HERE OR YOU HAVE TO GO BACK TO STEP 1 AGAIN  Open eclipse again    Using -refresh or -clean when starting eclipse did not help

User · Answer

UFT causing issues with RDz  Eclipse based  after install These suggestions will allow to work around this situation even with the environment variables in place and with corresponding values    Note  Conflicting application will not be recognized in a java context because it is being excluded from the java support mechanism    Impact  Excludes Add-ins support from hooking to conflicting application executable via Windows Registry Editor Requirement  The application must be started by an EXE file  except Java exe Javaw exe jpnlauncher exe   Instructions   a  Locate the executable filename of the application conflicting with add-in s  support  Either use the Task Manager or the Microsoft Process Explorer    b  Open Windows Registry Editor    c  Navigate to  HKEY LOCAL MACHINE SOFTWARE Mercury Interactive JavaAgent Modules For 32bits applications on Windows x64  HKEY LOCAL MACHINE SOFTWARE Wow6432Node Mercury Interactive JavaAgent Modules  d  Create a DWORD value with the name of the conflicting software executable filenmae and set the value to 0

User · Answer

You can try to start Eclipse first with the -clean option   On Windows you can add the -clean option to your shortcut for eclipse  On Linux you can simply add it when starting Eclipse from the command line

User · Answer

In my case deleting the  metadata folder of the workspace worked  I am using Eclipse Luna service Release 2

User · Answer

You can try to start Eclipse first with the -clean option   On Windows you can add the -clean option to your shortcut for eclipse  On Linux you can simply add it when starting Eclipse from the command line

User · Answer

no need to delete entire metadata file  just try deleting the  snap file from org eclipse core resources on your workspace folder  ex  E  workspaceFolder  metadata  plugins org eclipse core resources

User · Answer

In my case similar symptoms were caused by some rogue git repository with a ton of junk system files   Universal remedy  as mentioned above  is to use Process Monitor to discover offending files  It s useful to set the following 2-line filter    Process Name is eclipse exe Process Name is javaw exe

User · Answer

Windows -  Preferences -  General -  Startup and Shutdown   Is Refresh workspace on startup checked

User · Answer

On Mac OS X  you start Eclipse by double clicking the Eclipse application  If you need to pass arguments to Eclipse  you ll have to edit the eclipse ini file inside the Eclipse application bundle  select the Eclipse application bundle icon while holding down the Control Key  This will present you with a popup menu  Select  Show Package Contents  in the popup menu  Locate eclipse ini file in the Contents MacOS sub-folder and open it with your favorite text editor to edit the command line options   add   -clean  and  -refresh  to the beginning of the file  for example   -clean -refresh -startup          plugins org eclipse equinox launcher 1 3 0 v20130327-1440 jar --launcher library

User · Answer

It can also be caused by this bug  if you re having Eclipse 4 5 4 6  an Eclipse Xtext plugin version older than v2 9 0  and a particular workspace configuration   The workaround would be to create a new workspace and import the existing projects

User · Answer

It can also be caused by this bug  if you re having Eclipse 4 5 4 6  an Eclipse Xtext plugin version older than v2 9 0  and a particular workspace configuration   The workaround would be to create a new workspace and import the existing projects

User · Answer

Also look at http   www lazylab org 197 eclipse eclipse-hanging-on-startup-repair-corrupt-workspace   99  Recommended Solution works      i e  Removing  snap file  But if it did not worked then we have to try to remove indexes folder and further workbench folder

User · Answer

In my case  Juno  I had to do this   find  WORKSPACE DIR  metadata  plugins org eclipse core resources  projects   -name  indexes -exec rm -fr         That did the trick   Initially I thought it was a problem with Mylyn  I experienced these freezes after I started using its generic web connector   but the problem appeared even after uninstalling the connector  and even deleting the  mylyn directories   Edit  I also managed to restart eclipse by deleting just one file   rm  WORKSPACE DIR  metadata  plugins org eclipse e4 workbench workbench xmi   That worked fine  without any indexes involved  Only the workbech  which I personally don t mind that much

User · Answer

I also had luck with removing the   snap files   Mine were located in a different directory than mentioned in the posts  below     lt eclipse workspace gt   metadata  plugins org eclipse core resources  projects   Consequently  the following unix cmd did the trick   find  lt eclipse workspace gt   metadata  plugins org eclipse core resources  projects  -name    snap  -exec rm -f

User · Answer

This one works for me   Another  and a bit better workaround which apparently works    Close Eclipse  Temporary move offending project somewhere out of the workspace  Start Eclipse  wait for workspace to load  it should   Close Eclipse again  Move the project back to workspace    Source  Eclipse hangs while opening workspace after upgrading to GWT 2 0 Google app engine 1 2 8

User · Answer

In Ubuntu eclipse -clean -refresh worked for me for Eclipse 3 8 1

User · Answer

I tried all of the answers in this thread  and none of them worked for me -- not the snap files  not moving the projects  none of them    What did work  oddly  was moving all projects and the  metadata folder somewhere else  starting Eclipse  closing it  and then moving them all back

User · Answer

I had a similar problem with a rather large workspace in 3 5 and no  snap-files anywhere to be seen   Windows -  Preferences -  General -  Startup and Shutdown -  Refresh workspace on startup  seems to be a workspace-related setting and so I couldn t change it for the workspace that was causing the hang   Running eclipse with the command line parameter -refresh and then changing the setting seems to do the trick

User · Answer

In Ubuntu eclipse -clean -refresh worked for me for Eclipse 3 8 1

User · Answer

In my case deleting the  metadata folder of the workspace worked  I am using Eclipse Luna service Release 2

User · Answer

In my case similar symptoms were caused by some rogue git repository with a ton of junk system files   Universal remedy  as mentioned above  is to use Process Monitor to discover offending files  It s useful to set the following 2-line filter    Process Name is eclipse exe Process Name is javaw exe

User · Answer

Windows -  Preferences -  General -  Startup and Shutdown   Is Refresh workspace on startup checked

User · Answer

Removing   snap  mine is   markers   --clean-data or move workspace folder seems all did not work for me   As my eclipse stopped working after I installed and switched my keyborad input to HIME  I went back to fctix and it worked

User · Answer

I just had problems with Eclipse starting up  It was fixed by deleting this file   rm org eclipse core resources prefs  I found in  settings

User · Answer

I did a lot of these solutions and none seemed to work for me   What finally did work was to restart my Mac   Duh   I noticed that my jconsole also seemed to be stuck which made me immediately go for a restart because it seemed to be Java related as opposed to Eclipse specifically

User · Answer

Removing   snap  mine is   markers   --clean-data or move workspace folder seems all did not work for me   As my eclipse stopped working after I installed and switched my keyborad input to HIME  I went back to fctix and it worked

User · Answer

This may help  In your eclipse   1  Go to Help  2  Click Eclipse marketplace  3  search - optimizer  install  optimizer for eclipse

User · Answer

What worked for me was this-- On Ubuntu   Ctrl F1 ps -e kill -9 for process ids of eclipse  java and adb

User · Answer

my solution is to remove this dir   workspace  metadata  plugins org eclipse e4 workbench   what is did was first remove  move it to a save place  all from  metadata  eclipse started all new  all my settings gone   then i added bit by bit back into the  metadata dir until it dit not work again  this way i found i only had to remove this dir  And now Eclipse started with all my settings still in place   it seems that in the file in this dir the windows which should be opened on startup are listed and some how it could not find one off them so it hung  why i m unclear because the file which in complained about in the logging was on my filesystem

User · Answer

I also had luck with removing the   snap files   Mine were located in a different directory than mentioned in the posts  below     lt eclipse workspace gt   metadata  plugins org eclipse core resources  projects   Consequently  the following unix cmd did the trick   find  lt eclipse workspace gt   metadata  plugins org eclipse core resources  projects  -name    snap  -exec rm -f

User · Answer

try        cd to  lt workspace gt   metadata  plugins org eclipse core resources     remove the file   snap  or  markers in Indigo

User · Answer

I did a lot of these solutions and none seemed to work for me   What finally did work was to restart my Mac   Duh   I noticed that my jconsole also seemed to be stuck which made me immediately go for a restart because it seemed to be Java related as opposed to Eclipse specifically

User · Answer

I just had problems with Eclipse starting up  It was fixed by deleting this file   rm org eclipse core resources prefs  I found in  settings

User · Answer

In my case  Juno  I had to do this   find  WORKSPACE DIR  metadata  plugins org eclipse core resources  projects   -name  indexes -exec rm -fr         That did the trick   Initially I thought it was a problem with Mylyn  I experienced these freezes after I started using its generic web connector   but the problem appeared even after uninstalling the connector  and even deleting the  mylyn directories   Edit  I also managed to restart eclipse by deleting just one file   rm  WORKSPACE DIR  metadata  plugins org eclipse e4 workbench workbench xmi   That worked fine  without any indexes involved  Only the workbech  which I personally don t mind that much

User · Answer

My freeze on startup issue seemed to be related to the proxy settings  I saw the username password dialog on startup  but Eclipse froze whenever I tried to click ok  cancel  or even just click away from the dialog  For a time  I was seeing this authentication pop-up with no freeze issue   To fix it  I started eclipse using a different workspace  which thankfully didn t freeze on me  Then I went to Window -- gt  Preferences -- gt  General -- gt  Network Connections  I edited my HTTP Proxy entry and unchecked  Requires Authentication   Then I started my original problematic workspace  which launched this time without freezing  Success   I had no further issues when I re-opened my workspace  and was able to re-enable authentication without having a problem  I didn t see the username password pop-up anymore on start-up  so there s a chance my authentication info was FUBAR at the time   Using  MyEclipse  Version  2016 CI 7  Build id  14 0 0-20160923

User · Answer

Since I don t have a  snao or  prefs file in  metadata plugins org eclipse core resources folder  running on OS X   what did the trick for me was copy the  project folder to old project  start Eclipse  and check      Windows -  Preferences -  General -    Startup and Shutdown -  Refresh   workspace on startup   as proposed by matt b  After that  I closed Eclipse  renamed the folder old projects back to  projects and after that everything worked fine again

User · Answer

My freeze on startup issue seemed to be related to the proxy settings  I saw the username password dialog on startup  but Eclipse froze whenever I tried to click ok  cancel  or even just click away from the dialog  For a time  I was seeing this authentication pop-up with no freeze issue   To fix it  I started eclipse using a different workspace  which thankfully didn t freeze on me  Then I went to Window -- gt  Preferences -- gt  General -- gt  Network Connections  I edited my HTTP Proxy entry and unchecked  Requires Authentication   Then I started my original problematic workspace  which launched this time without freezing  Success   I had no further issues when I re-opened my workspace  and was able to re-enable authentication without having a problem  I didn t see the username password pop-up anymore on start-up  so there s a chance my authentication info was FUBAR at the time   Using  MyEclipse  Version  2016 CI 7  Build id  14 0 0-20160923

User · Answer

Well  I had similar behaviour while starting eclipse over X11  I forgot to tick the enable X11 forwarding in my putty

User · Answer

The freezing   deadlock can also be caused by this bug on GTK3   Xorg https   bugs eclipse org bugs show bug cgi id 568859 Can be workarounded by using Wayland session  although in my case Eclipse fails to detect reasonable font for some reason and looks like this   Related  https   www reddit com r swaywm comments bkzeo7 font rendering really bad and rough in gtk3  https   www reddit com r swaywm comments kmd3d1 webkit gtk font rendering on wayland

User · Answer

I had no snap files   Going through the help menu installation list  at least 90  of my plugins had the uninstall button deactivated so I could not handle it through there   Under startup shutdown most of plugins were not listed   Instead  I had to manually remove items from my plugins folder   Wow  the startup time is much faster for me now  So if everything else does not work and you have plugins that are disposable  this could be the ultimate solution to use

User · Answer

JAVA VERSION COULD BE PROBLEM   I tried few answers given above  But it didnot work  But meanwhile I was trying them it clicked to me that I switched the java version for some other stuff  amp  forgot to switch back  Once I jumped back to the previous version  Eclipse started working for me

User · Answer

This one works for me   Another  and a bit better workaround which apparently works    Close Eclipse  Temporary move offending project somewhere out of the workspace  Start Eclipse  wait for workspace to load  it should   Close Eclipse again  Move the project back to workspace    Source  Eclipse hangs while opening workspace after upgrading to GWT 2 0 Google app engine 1 2 8

[java] How do I prevent Eclipse from hanging on startup?

Examples related to java

Examples related to eclipse

Examples related to eclipse-3.3