We Keep Coding

Eclipse neon hangs loading org.eclipse.ui.navigator

Researching existing answers to problems with eclipse hanging on startup, I have not found anything that seems applicable to my problem. Neither have the responses so far been helpful.
The splash screen appears and seems to be conducting a normal startup process, but when the status message reports
Loading org.eclipse.ui.navigator
all progress halts, apparently forever.
REACTIONS TO ADVICE AND DIAGNOSTICS:
A related question caused me to add -clean to the shortcut. This did not help.
The first actual answer suggested reinstalling Eclipse. This did not help.
The second response suggested that I look at Eclipse log files. The first file suggested was most recently updated May 5, long before the problems started, and the second suggested file did not exist.
Moving the old workspace to a different file name and reinstalling Eclipse again with a brand-new workspace enabled me to launch Eclipse successfully, but if I switch workspaces to the new workspace, it hangs (at the same point).
The problem appears to be loading a plugin named org.eclipse.ui.navigator. There is no such plugin in {workspace}\.metadata\.plugins, in either the old workspace or the new workspace. I don't know why Eclipse is trying to load that nonexistent plugin when it tries to run from the old workspace but not from the new workspace. As far as I can tell I need to find some way to install the navigator plugin in the old workspace (without being able to run Eclipse from that workspace), or somehow tell Eclipse not to try to load it. I have no idea how to do either.
Running Eclipse Neon, on a Win10 machine; Eclipse ran normally as of a few days earlier and only started hanging May 22.

Had the same problem today. It was resolved after removing the following folders from the [workspace]/.metadata/.plugins folder:
org.eclipse.e4.ui.workbench.swt
org.eclipse.e4.workbench

Error message displayed when opening Eclipse: "An error has occurred. See the log file null"

I use Windows 10 and jre1.8.0_51. I don't know why when I start Eclipse it always displays an alert message "An error has occurred. See the log file null."
And I cannot open Eclipse thereafter. I tried to search Google and have no best solution. I uninstalled JRE and installed it again, but it still produces the same problem.

Try to launch it from the console like:
C:\path\to\eclipse\eclipse -clean
Also you try to can delete the file to fix the problem permanently as suggested here. Command would be something like below for windows.
del YOUR_WORKSPACE/.metadata/.plugins/org.eclipse.core.resources/.snap

I ran into the same problem. When I try running eclipse as Administrator, the problem went away.

Had same issue.
To resolve it : Go to Eclipse directory -> Open CMD -> eclipse -clean
worked well.

I had the same issue with Windows 10. Give full control to your user in security settings on the eclipse and workspace folders.
I also found the read only property was set on the eclipse and workspace folders, which I unset.
The log file can be found in the eclipse\configuration folder.

I deleted .metadata from the workspace and ran the eclipse as run as administrator and it worked for me.

I found that running Eclipse (STS 3.9) as administrator worked, which is a permissions issue. Giving the required users read/write/execute permissions to the config and workspace folders did the trick (they couldn't write previously).

I too came across the same error.
My log file says :
Java.io.FileNotFoundException: C:\Eclipse\eclipse-jee-luna-SR2-win32-x86_64\eclipse\configuration\org.eclipse.osgi.manager.fileTableLock (Access is denied)
So, i copied entire eclipse in another folder and it worked for me.
So, for me the problem was write access, because eclipse need write across configuration folder, in my case eclipse was unzipped by some other user and i didn't have the access.

I encountered the same problem, and then I found out that, the eclipse distribution works fine with JDK 8. I previously ran JDK 10 and I got this error. Uninstalling JDK 10 and installing JDK 8 fixed the issue for me.
Hope this helps!!

Make sure your eclipse launch folder does not have read only property/attribute
My eclipse resides at below location and If I right click ->properties- checked attributes were read only. I unchecked read only and restarted eclipse. Issue was resolved.
C:\Users\Ashish\Downloads\eclipse-jee-mars-2-win32-x86_64 (1)\eclipse

Here I'm just share, if you can not copy file .metadata on mac because that file invisible (JUST on Mac issue), try this step:
compress your file .metadata backup
copy file .zip
paste file .zip to path/workspace
double click file .zip
done :-)

Open the eclipse.exe with the right mouse button and open with admin rights and that's it!

I had the same problem and deleting the file .metadata/.plugins/org.eclipse.core.resources/.snap and try it should work

Uninstall Java JDK
Reinstall JDK 8
Run Eclipse as administrator

Remove the .snap file from <WORKSPACE-DIRECTORY>\.metadata\.plugins\org.eclipse.core.resources

The mentioned solutions didn't work for me under Windows OS.
I just deleted .manager from eclipse\configuration\org.eclipse.core.runtime and from eclipse\configuration\org.eclipse.osgi and the issue was fixed.

Delete the .metadata folder in eclipse. That should resolve the issue. The .metadata folder is recreated by eclipse once it is able to launch successfully.

I too got the same error in My Windows 10 pc while using Eclipse 2020 version
Just delete the .metadata folder and then try to run eclipse again it will solve the problem and run fine. .Metadata folder will get created once again by itself as we open eclipse.

I uninstalled JRE and installed it again, but it still produces the same problem.
Turns out that my version of eclipse doesn't work with jdk17 (installed it using Amazon Corretto 17). So uninstalled Amazon Corretto 17 (automatically uninstalls jdk17 as well) and installed jdk11 using Amazon Corretto 11.
Thankfully worked for me! What I tried was similar to what you tried, but worth trying anyway.

Re-install Eclipse or add vm path in your eclipse.ini file.
-vm
C:/<Your Path>/jdk1.8.0/jre/bin/javaw.exe
Note: Change javaw.exe path according to your system

Make sure your java version is compatible with your eclipse version!
An easy solution that worked for me. Deleting the .metadata did not result. I was using eclipse MARS 2.0 but set my JAVA_HOME to java 17. However, Mars does not support java 17. As soon as I swapped it back to java 14 eclipse launched again.

Eclipse get hang after some time with error of java

I am using Eclipse Juno for android development purpose.
I am working on the project contain 4-5 library in it. Do know what is the reason but after several use of that same project My Eclipse get hang. Another thing is it only get hang while i am trying to run the app from eclipse.
After that my Eclipse get stop working and in Not Responding condition. When i click on that, I got below message by closing of Eclipse.
Message:
I don't know what is the reason for causing of this. Please help me regarding this issue.

It is because of a corrupted workspace. For, solution refer
this
The error was due to a corrupt workspace. As I disable the workspace check in the startup I couldn’t select another workspace since Eclipse wouldn’t start. Rename the workspace e.g. to “workspace1″. Eclipse will start and create a new uncorrupted workspace and work without any problems. Afterwards you can import your project into your new workspace and in the end remove the old corrupted workspace.
So, you have to create a new workspace

The most common reason I've seen Eclipse crash is due to running out of memory. Try editing the eclipse.ini file in your Eclipse installation directory, and changing the part where it says -Xmx512m to -Xmx1g (or 2g, if you have a lot of free memory on your system). You can also increase -Xms40m to -Xms512m or similar to make Eclipse start with more allocated memory initially.

Close your project from eclipse and try again. If it doesn't work, copy your projects into a new workspace and open them from there

An error has occured. Please see log file - eclipse juno

Whenever I start up Eclipse Juno, it gives me an error saying:
An error had occured. Please see the log file:
C:\Program Files\eclipse\configuration\1362989254411.log.
Some websites say to uninstall jdk and install it back again. I did that, but it didn't work. I think it was because on their website, the error is happening IN the workspace. Mine is on the program files folder, which is in the computer.
It happened after updating it. Should I downgrade. If so, how? If I can't downgrade, what should I do?

Try deleting following file from workspace.
YOUR_WORKSPACE/.metadata/.plugins/org.eclipse.core.resources/.snap
Or try launching it from console.
C:\path\to\eclipse\eclipse -clean

Solved :
Quit eclipse
GO to your workspace and delete .metadata folder
Now open eclipse with same Workspace path ( You will see as a new workspace )
Now right click import > General > Existing Projects into Workspace > next > Select root directory -> browse to your current workspace and press OK.
Now you will all see your all projects and then hit OK again.
Voila, same projects with same workspace no migration or reference problem.
After trying everything else, this solves my issue.

Delete the .metadata folder from workspace and start the eclipse and now again import all project in same workspace, this worked for me.

In my mac machine, I checked whether I installed two java versions or not. I got this error. Because i installed two java at a time.
User -> Library -> Java -> JavaVirtualMachines -> version 1.8.0 and version 11.0.1 has been installed.
I removed version 11.0.1. Now its working fine.

I deleted the entire .metadata folder, and it worked for me.

The best way is to delete all the *.snap files from /.metadata/.plugins/

Here's what I did to solve this:
I removed workspace/.metadata
run eclipse as an administrator.

In my case my JAVA_HOME was pointed to jdk9 after pointing JAVA_HOME to jdk8 resolved my issue.
Hope it helps someone.

i found the solution. i have installed 2 versions of jre sdk 1.3 and jre7 so i uninstall the older version sdk1.3 then it works.

C:\path\to\eclipse\eclipse -clean
Then change the working project directory to something different. It should work after that.

This instruction works 100% for me:
Rename the Eclipse workspace name
Start Eclipse (it will start successfully with empty workspace)
Exit it and change workspace name to previous state(if ask to replace some files, press no)
Start Eclipse again and Re import projects in current workspace
Enjoy!

Sounds simple but just delete/uninstall eclipse and install it again.

I was getting the same error while opening the eclipse. to solve that I checked the log file inside the metadata folder. where I found that there is version mismatch of Java. so I have changed the VM inside my eclipse ini file.
-vm
/opt/jdk1.8.0_191/jre/bin
Hope this will also help to solve your problem.

For me it was down to a locking/permissions bug on
(path to Eclipse IDE)\configuration\org.eclipse.osgi.manager.fileTableLock
See here
Spring Tool Suite 4 (64 bit for Windows Server 2016)
Version: 4.2.2.RELEASE
Build Id: 201905232009
based on Eclipse
Version: 2.2.500.v20190307-0500
Build id: I20190307-0500
wouldn't launch and a pop up dialog appeared saying:
launch error has occurred see log file null
(This became apparent from the latest text log file in the folder
(path to Eclipse IDE)\configuration)
!ENTRY org.eclipse.osgi 4 0
2019-06-19 18:41:10.408
!MESSAGE Error reading configuration: C:\opt\sts-4.2.2.RELEASE\configuration\org.eclipse.osgi\.manager\.fileTableLock (Access is denied)
!STACK 0
java.io.FileNotFoundException: C:\opt\sts-4.2.2.RELEASE\configuration\org.eclipse.osgi\.manager\.fileTableLock (Access is denied)
...
I had to go and tweak the permissions via File Explorer (Full access).
It appeared as if the IDE was doing nothing for a while.
The splash screen for Spring Tool Suite (based on Eclipse) eventually disappeared and the IDE started up again.
Now everything is back working correctly again.

None of the current answers worked for me. On CentOS, I had to delete the .eclipse folder from home directory. Then eclipse launched just fine!

I got the same error when I was using Texas Instrument's Code Composer Studio which is built on eclipse. It happened when I changed my Workspace folder to be inside the Google Drive folder. Deleting files from YOUR_WORKSPACE/.metadata/.plugins/org.eclipse.core.resources/ did not work for me.
The following worked for me:
Take backup of original Workspace folder
Delete the original Workspace (from the Google Drive folder)
Start Eclipse (works fine now)
Restore the Workspace backup to a non Google Drive folder
However deleting and restoring the Workspace folder is not advisable since it can have other complications. But I was desperate.

I had 2 version of JDK installed - JDK 7 and JDK 8. Initially it worked even when both the versions were there and was able to use Git and Gradle and up the Spring Boot Application.
Then after system restart/sleep, workspace prompt did not come up.
Uninstalled JDK 7 and it prompts for workspace,now.

I have got the same error after removing eclipse and installing it again.
Deleting the .metadata directory and running eclipse -clean does not work for me, but the following works for me:
sudo cp /usr/lib/jni/libswt-*3740.so ~/.swt/lib/linux/x86_64/
if you have a 32 bits based system do:
sudo cp /usr/lib/jni/libswt-*3740.so ~/.swt/lib/linux/x86/

In my case I didn't want to remove eclipse because in corporate world we can't control everything. Also deleting some files from workspace .matadata could not help. So below hack that I found with trial and error worked for me perfectly :
Go to this path: C:\....\eclipse-Luna\configuration\org.eclipse.core.runtime\
now delete .manager completely.
Start eclipse again and woilaa.. it will run normally.
[In my case, I use eclipse luna. I once abruptly closed the PC when eclipse was open. Then eclipse was not able to start on the next system restart. So keep in mind to close eclipse properly. :) ]

My OS architecture is 64-bit so downloaded Eclipse Oxygen 64-bit version and got this error. Tried various solutions posted here but didn't help. Then downloaded Eclipse Oxygen 32-bit version and it works well.

For me the problem was that I installed Java sdk 1.9 before installing eclipse. deleting it and installing Java sdk 1.8 instead fixed it.
Also, if you are using mac, try
export JAVA_HOME=$(/usr/libexec/java_home)
and then
echo $JAVA_HOME
your should get something like
/Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home

For STS on MacOS, i followed the following steps:
Go to the STS directory from terminal:
cd /Users/karan.verma/Documents/sts-bundle/STS.app/Contents/MacOS
Start STS
./STS
STS started, but all my imported projects were removed.

The reason may be that you are trying to use old version of Eclipse for new version of Java. I've downloaded the latest Eclipse (which is Oxygen) and it worked for me.

It worked for me when I went to WorkSpace\.metadata\.plugins\org.eclipse.e4.workbench and then remove the *.xmi files.

Deleting metadata folder might not work in this case. Or eclipse -clean command. Or reinstall eclipse might not solve this.
Instead try deleting other java versions you might have in your machine.
Check what you have right now using this:
/usr/libexec/java_home -V
Delete other java versions which you don't want, following below command:
sudo rm -rf /System/Library/Java/JavaVirtualMachines/java-version.jdk
This should resolve your issue.

The issue is due to the availability of more than one eclipse versions. I tried removing both installations and started with a clean install and it worked. Also, make sure after the install point to a new workspace.

In my case, error was due to Java 14 , which is not an LTS, downgraded it to java 8 and it worked.

It happened to me after I rename the file folder. I Try to delete my workspace or .metadata or .manager folder, and not work.
Then I download the program again and I choose the complete download. It is 337.511 KB and in zip File. But I place it in Flashdisk. I open the zipfile then I run eclipse.exe. It work. Then I import all my work file. It work back again show in Project Explorer.
I close eclipse. Then I click eclipse icon in desktop ( I didn't delete the program). Now It work fine.

If nothing works, then try uninstalling and then reinstalling Eclipse.
This is how i just fixed this problem after trying everything suggested on this forum.

How do I prevent Eclipse from hanging on startup?

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?

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:
<workspace>\.metadata\.plugins\org.eclipse.core.resources\.projects\<project>\.markers.snap

try:
cd to <workspace>\.metadata\.plugins\org.eclipse.core.resources
remove the file *.snap (or .markers in Indigo)

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.

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.

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

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

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.

I also had luck with removing the *.snap files. Mine were located in a different directory than mentioned in the posts (below).
<eclipse workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects
Consequently, the following unix cmd did the trick:
find <eclipse_workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects -name "*.snap" -exec rm -f {} \;

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.

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.

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.

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

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.

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

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

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.

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.

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.

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!)

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.

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

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.

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

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

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.

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

In Ubuntu eclipse -clean -refresh worked for me for Eclipse 3.8.1

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.

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

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