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.
Related
I use IntelliJ IDEA 15 and have a problem with the auto-saving. For example I make a new configuration, e.g. Show the line number. When I close IntelliJ and reopen my IDE, it doesn't save my configuration and shows me this message:
Unable to save settings : Failed to save settings . Please restart IntelliJ IDEA
I get this too (IntelliJ 15.0.5), but only when the "Markdown support" plugin is used. Once a .md file is visualised the error starts appearing.
For future reference current version: 2016.1.20160405.143
Not a very solution-oriented post, but maybe this can help someone further pinpoint the source of the error.
This workaround allows you continue using "Markdown Support".
Uninstall the latest version of "Markdown Support" and install version "8.0.0.20160127.143.1" from https://plugins.jetbrains.com/plugin/7793?pr=idea. Everything works fine.
I was receiving the error with:
IntelliJ v15.0.6
"Markdown support" plugin version 2016.1.20160405.143
I uninstalled the Markdown support plugin (IntelliJ IDEA > Preferences... > Plugins > Markdown support), restarted IntelliJ, and am now able to save without error.
I have tried everything from this SO thread but it did not work. I solved it by deleting the .idea folder from my project's Windows path and then restarting intellij.
This can also happen when the disk drive where the currently opened project is stored is full (0 bytes left on device). The system tries to write to the .idea folder but cannot, so it gives the same error as if there were no access rights.
This happened to me as there was a process writing to disk in the background until it was full.
I delete this file : .IntelliJIdea
When I launch ./idea I should reconfigure all IntelliJ system (config/ extention/ theme/ licence ...)
So It's okay now but I think is not a good solution ...
Workaround for Windows users.
My installation is located in:
"C:\Program Files\JetBrains\phpstorm"
The location gives it problems with the saving of files. (probably to do with user rights and UAC, not totally figured out what rights the folder needs, but for easy resolving I removed and reinstalled Phpstorm to
"C:\development\phpstorm" and it resolved the issue.
For those who have a simular issue on windows machines:
I have applied the "hidden" property for the .[IntelliJ-Produkt][Version] folder in Users/[Username] folder. This was causing the issue. Don't do that.
I encountered this problem when I open up IDEA for the first time after copying the old config files backed up with my Live CD USB before reinstalling my Ubuntu. I think it is because I copied the files from the old OS and to the new OS as root, so the ownership of the folder is changed. Now when I want to write to it as another user, it blocks me from doing it.
Change the ownership to your user and change permission to add write solves it. You use chown and chmod.
On OSX, I've uninstalled PhpStorm, and then have installed it again, always by using the JetBrains TOOLBOX.
Hope it helps!
Windows Defender was the issue
Windows defender has a protection component called ransomware protection (details: https://www.makeuseof.com/tag/protect-ransomware-windows-defender/)
This restricts folder access (for selected folders) to some programs only.
Add Webstorm to allowed applications
Excerpt is below. Full guide with pictures are here: https://www.windowscentral.com/how-allow-blocked-apps-ransomware-protection-windows-10-october-2018-update
Open Windows Security.
Click on Virus & threat protection.
Under "Ransomware protection," click the Manage ransomware protection option.
Click the Allow an app through Controlled folder access option.
Click the Add an allowed app button.
Click the Recently blocked apps option.
Click the + (plus) button for the app you trust and want to allow.
Click the Close button.
I faced the same issue today and it might help some people if above solutions cant help. I am using dual boot system. Win 8 and Kubuntu. I got this problem with my intellij installed in Kubuntu. I realized my project was in a NTFS partition which was marked as READ ONLY. This happens sometimes when you shutdown windows and start computer into your linux.
Solution is to go back to your windows OS and restart it and switch to linux. Also, you could hold shift and press shutdown button, then choose to turn of your pc in the blue menu.
On windows 10 I had the same problem, I ran PhpStorm as administrator which fixed permission issues it had.
Then I restarted PhpStorm without administrator permissions and everything worked fine.
It was a fresh install so no plugins other then the build in ones.
I've encountered this issue multiple times; rebooting my (windows) computer has always worked for me (while restarting Intellij didn't do anything).
It's because you don't have permission to save settings. On my macOS, I set write permission of my project.
I got same error message for InteliJ WebStrorm saying
Unable to save settings
Failed to save settings. Please restart WebStorm
It happened due to permission issue. if you don't have permission to save this message could pop-up. Please make sure you have write permission to the folder you are saving.
I might be late at answering this but I did not see any accepted answers here.
I got a solution to this on other forum.
They suggested to start IntelliJ IDEA as Administrator.
It worked for me.
Hope it helps people who come here searching for answers.
for my Ubuntu, i fixed it by issuing this command.
sudo chmod 777 /path/to/dir
I'm trying to install a plugin in Eclipse Luna. I installed Papyrus and am trying to install SWT designer, but before the download/installation is completed I get an error:
An error occurred during the
org.eclipse.equinox.internal.p2.engine.phases.CheckTrust phase.
session context was:(profile=epp.package.standard,
phase=org.eclipse.equinox.internal.p2.engine.phases.CheckTrust,
operand=, action=). Error reading signed content. error in opening zip
file
After this error I can't install anything and the install manager does not work anymore and shows me the same error all the time only one way I delete the current Eclipse directory and extract it again.
This time I install Papyrus, SWT designer and some other, but I get the error between install another plugin again. This is wrong if I get an error on install any of plugin reinstalling Eclipse and the other plugin again.
Is this a bug or a problem?
OK finally i found the solution for solve this problem. I don't know why Eclipse is showing me this error and i don't know if this is the best solution. I solve my problem with delete the artifacts.xml file in Eclipse root directory.
After deleting this file try to install that plugin again but this time after few second everything completes and works perfectly.
UPDATE:
If you get that error again then just go to Eclipses' root directory and search for "artifacts.xml" and delete all the files is in the result ;)
Remove the artifacts.xml from the folder.
Keep a copy of it in some other location (preferably external devices such as pendrive or hard disks etc).
Restart Eclipse.
Install the software plugin you want to install (it will ask for permission again).
After installation paste the artifacts.xml file back into the eclipse folder.
Restart eclipse and set the SDK location.
Code to death!!! ;p
Run Eclipse as an administrator, then try to install the plugin again via help->Install New Software. it worked for me
I installed E4 RCP Patch(bugzillas 445122)(Install new software -> Eclipse 4.4.1 Patches for bug 445122) and this helped me.
I ran across this problem while updating eclipse's internal software. I discovered that the jar file org.eclipse.epp.mpc.help.ui_1.5.2.v20161004-1655.jar (found in the error details) in the eclipse plugins directory was corrupted (7-Zip was unable to inspect its contents). I redownloaded and manually replaced this file with one downloaded from their site, and I was then able to install the software without an issue. Hope this helps :)
(If it was a different JAR file for you, you can click "show directory contents" on this page and download the one you need.)
The reason for this error is typically a damaged jar in the bundle pool. You can fix this without manually editing files:
run the Eclipse installer ("Oomph")
select "Bundle pools" from the menu
hit the "Analyze agent" button
wait until the column "Damaged Artifacts" doesn't show a percent number anymore (scanning has finished)
You can now filter the bottom view to show only damaged artifacts, and choose to either delete or repair them (repair means to download them again from the Internet).
Recently i had this issue & i did a few workaround to make things right,
Drag and dropped from official page, normally eclipse restarts after the download, and a pop-up will ask us to select the svn connectors from list. but that didn't happened to me.
Install svn Plugin. (By drag and drop or install new software or any)
After this goto window->preferences->Team->svn
select Connector Tab and click Get connectors Button then the prompt will appear select any one connector to get it done (i use NativeHL 1.8).
I solved this problem by editing the artifacts.xml.
Close Eclipse.
Edit the artifacts.xml.
Find and delete previous entries related to the plugin you are
trying to install.
Save artifacts.xml.
After this you should be able to start Eclipse normally and install your plugin.
I tried many solution from here including the one which says removing artifacts.xml and try installing with opening software with Run as Administrator also tried to install from the Help option "Install new software" none of this worked for me.
Then I updated to the latest version of JDK and it worked perfectly.
I hope this help you.
Thanks.
Vijay P.
org.aspectj.weaver_1.8.10.201704242114.jar
File will be downloaded for google, and it can be placed in eclipse/plugin/org.aspectj.weaver_1.8.10.201704242114.jar can be replaced with older jar file.........it can be solved for your problem...........
Try this from the Eclipse marketplace
1. Click Help>Eclipse marketPlace (Eclipse marketPlace dialog box will open)
2. Type the name of your plugin (ex: type SWT Designer) in the find edit box, make sure to keep default values for All markets and all categories, and click go button.
3. The page will refresh and display all plugins that have swt designer in their name.
4. Click intsall or update button on the one that fits your needs.
5. The installation or update will be done successfully.
6. Restart your eclipse
7. The installation will be fine.
It's a failure in Eclipse.
Try to uninstall it then download it from: https://www.eclipse.org/downloads/
and install it.
I have a problem trying to launch Eclipse in Ubuntu 14.04. Splash picture pops up, then blinks, turns white - and nothing happens until kingdom come.
I have tried Luna, Kepler and 3.8 (from Ubuntu repository). EE and SE editions - both the same. I have also tried to launch them with different (oracle) vm - 1.7 and 1.8.
And yes, I have tried the -clean and simple workspace removal.
This is the only thing it says in console:
org.eclipse.m2e.logback.configuration: The
org.eclipse.m2e.logback.configuration bundle was activated before the
state location was initialized. Will retry after the state location
is initialized.
Java VM works fine - I can launch (for example) IDEA or java\javac commands.
Any suggestions?
The answer is already here, but it's in the comments. So I re-post it as answer:
check your 2nd screen. Workspace dialogue may be there.
Try this:
1) Remove .snap from:
.metadata\.plugins\org.eclipse.core.resources\.projects\<project>\.markers.snap
If you can't find it manually try this:
find /.metadata/.plugins/org.eclipse.core.resources/.projects -name "*.snap" -exec rm -f {} \;
It Generally happen when eclipse is closed unexpectedly.
Heres things you can do.!
1)Save and Delete .metadata from workspace folder.
2) Try Re-installing Eclipse.
This solution worked for me. :)
If you don't have any pending changes and have pushed your project already on your repo, you can also try deleting the project folder where eclipse opens a project path automatically.
When you run eclipse again, it will work again.
Unfortunately, deleting metadata didnt work for me. Also I don't have any extra monitor so deleting my project folder was my last resort.
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.
I've been trying to open Eclipse to start my work today, and it freezes everytime during load.
My Eclipse is Helios. Someone told me I should remove a file called .lock from .metadata folder, but still didn't work.
Does anyone have any idea of how do I "melt" this thing up?
ps: I opened it yesterday with no problems.
Have you already tried to start Eclipse with a -clean parameter? Sometimes this can resolve some issues..
I would suggest a (big) problem with a plugin in Eclipse.. because project plugins or runtimes will execute later.
Create a new workspace and repimport your projects from your old workspace. If you have a vcs, you can re-checkout them.
Start it with the -clean option.
It should take a bit longer (depends on your eclipse configuration and workspace, but if nothing is really broken, it will get it to work).
I believe something is wrong with your workspace. I typically remove current and create new one in such case. It usually takes up to 5 minutes (if I have to add 20 projects). In most cases it takes less.
I have experienced something similar when launching Eclipse after having to force close it for some reason.
If it always hangs when loading the SVN plugin — like in your screenshot — it is likely to be related to that. In this case I suggest the following:
back up your current workspace
launch Eclipse with the -data command line argument to specify a different workspace folder
if Eclipse starts up successfully, try to import your projects from the original workspace or even better from SVN