I launched Eclipse earlier to jot down a snippet and was faced with the following as an error when I tried to run a fresh project:
An internal error occurred during: "Compute launch button tooltip".
That popup window shows as soon as I mouse-over the run icon in the top bar, or if I right click on the class in the explorer window and select any of the run/debug options.
After doing some research on the error, I see several people who posted similar messages but they all have been fresh installs of Eclipse. So note that this is not a fresh install, and that Eclipse was working fine earlier today. Also note that not only does my new project not run (with the normal main method), but projects I was running earlier have all stopped working with the same error.
Finally, also be aware that after seeing other people's suggestions on fixing this, one specifically said to select run configurations from the top of the page run menu. When I selected run configurations from this dropdown, I got the following message:
Exception occurred creating launch configuration tabs
Reason: Plug-in org.eclipse.jdt.debug.ui was unable to load class org.eclipse.jdt.internal.debug.ui.launcher.LocalJavaApplicationTabGroup
After that message, the run window opens but all of the tabs are missing. Like where you can set the display width and height, and the other tabs, they are all missing from the window now.
I was using Eclipse trouble free earlier today and I am sure no updates took place between when Eclipse was working and now. My question is of multiple parts: What is wrong in a nutshell? What could have caused this?
Got this from another site of some guy who got this same error after upgrading.
Worked for me as well.
Apparently putting the following line in your eclipse.ini helps:
-Dcom.ibm.icu.util.TimeZone.DefaultTimeZoneType=ICU
Try setting the launch properties in:
Window>Preferences>Run/Debug(Expand)>Launching(Click)
Under launch Operations menu set it to:
Always launch the previously launched application
Click:
Apply>Ok
I never found out what went wrong, but a reinstall of eclipse fixed it. All projects survived seemingly undamaged.
Thanks for the reply on the .ini but that did no good.
I had same error today - in an eclipse installation (Juno SR2 64bit) that has been running fine for months.
0: There were no changes on svn for my projects since yesterday (when it was running fine).
1: I restored the workspace from a 'Windows 7 -> Properties -> previous copy' backup. This failed because the directory structure of the '.metadata' contains folders with a deeper structure than is supported.
2: I restored the workspace from a overnight archive (gzipped so file depth is not an issue).
This had no effect.
3: I tried to restore the eclipse installation directory (which seems to be updated an awful lot) from a 'Windows 7 -> Properties -> previous copy' backup. Again this failed - because of folder-depth issues (Note: it is installed in the root directory of my disk - so there is actually no way to use a restore on this installation!)
4: Had to delete the .metadata from my workspace and reinstall eclipse (and all the additional plugins), and re-import my projects, and setup all the servers, and android, etc, which took many hours.
The moral of the story? Backup both your workspace AND the eclipse installation every night manually. Windows Restore will NOT save you. Backing up your workspace is NOT enough.
I had the same problem using eclipse mars. I cleared the folder .recommenders\index
And that solved my issue.
Hope it helps.
incase you are having the eclipse files which you have downloaded from the official site .Just extract those file in the same folder where your previous eclipse was installed and select replace all.
best solution
I also encountered this issue, the reason why this issue occurred on my project was due to I was missing the JRE System Library in the root folder of my project.
To solve this issue, make sure you have the libraries like JRE System Libraries on the root folder of your project.
I am using the BB eclipse plugin to create a BlackBerry app. I made some changes to my app but they were not reflected in the simulator. So I ran clean.bat and rebuilt the project. But now the project's cod file is not getting generated.
And if I try and view the BlackBerry project properties for the Project, I get an error saying the window contains invalid values and it doesn't let me see the BB properties of the project.
The only solution I've found in the support forums is to create a new project and copy the whole code to this workspace. But that doesn't look like a very good solution.
It seems to be a bug in the blackberry eclipse plugin. I had the same problem and "fixed" it creating a new project.
Sometimes it works launching the simulator and erasing the application in the simulated blackberry. Another trick is to delete .jar, .jad and .cod refresh and then clean all.
The last tricks that also works is to open the same workspace with the Blackberry IDE and it may repair it.
Sorry, I don't have a definite solution but I hope you can solve your problem with one of the tips.
You have to follow some steps as:-
Delete deliverables folder.
Remove all .jad files from your system. Search all .jad files in system.
Go to eclipse\plugins\net.rim.ejde.componentpack6.0.0_6.0.0.30\components\simulator and run clean.bat. It will reset the clean simulator.
Clean all projects from workspace.
I'm serious. I installed the Blackberry web developer thing for eclipse (being stupid, and not seeing the 'web' part). Then, when I realized my mistake, I went and got the JDE for Eclipse. I went through the install process....open up Eclipse...and I'm lost. I don't know how to run code...or the simulator, or anything.
All the tutorials I'm finding are referencing an older "beta" version of the Eclipse plugin, which apparently had a "Blackberry" menu option. I'm not seeing that.
I found some sample code, which gives the helpful instructions:
"1. Extract HelloWorld_incomplete.zip
2. In the IDE, open the helloworld.jdw workspace
3. Open the helloworld.java source file.
"
...I've never seen a .jdw file before. If I try opening it in Eclipse, I get a not-very-useful text file. Since they say it's a workspace, I try the "Switch Workspace" option in Eclipse, which lets me pick a folder, rather than a file.
I'm pretty sure "Import Project" isn't right, either.
So, I figure I'll deal with that later, so I open up the source code (a standard .java file, with a main, etc). I try running it, but it asks for an Ant build file.
I can run standard Java files just fine (that is, I know Java is in my path).
I don't know if maybe I don't have the Blackberry part right...or if it's on the eclipse side where I'm failing.
Does anyone have any ideas?
-Jenny
Edit: Just to be sure, I tried downloading the plugin through eclipse with their provided link (http://www.blackberry.com/go/eclipseUpdate), but eclipse says that it got a .jar file when it was expecting a .zip file, and so it errored. Can you even unzip a jar file (like Eclipse is trying to do?)
It sounds like you have the wrong package.
I installed it yesterday from the "Download Now" button at http://na.blackberry.com/eng/developers/javaappdev/javaeclipseplug.jsp
and it had both the menu option and the Blackberry project type.
It should have an installer if you get the correct one. I would post a direct link, but RIM likes to ask for your info before allowing the download.
Try installing it to a different directory and using a new workspace. It could be that the old install is interfering somehow.
-Hope that helps
if you want to know step by step to install the jde plugin in eclipse you can visit http://learn.virtue-software.com/2011/05/quick-start-creating-blackberry-application-with-eclipse/
I am using eclipse 3.4.1 Java EE under Vista. It seems to like getting stuck when building my workspace. Canceling the build doesn't seem to do anything as well.
Why is this happening and how do I fix the problem?
I was able to fix this with the following:
First, exit Eclipse. Then temporarily move the following .projects folder to a safe location:
mv .metadata\.plugins\org.eclipse.core.resources\.projects projects
Start and exit Eclipse, then move the .projects folder back to where it was originally:
mv projects .metadata\.plugins\org.eclipse.core.resources\.projects
Use at your own risk, of course.
Some time it's very helpful to execute eclipse from command line with "-clean" parameter to enforce it produce clean up for workspace.
eclipse -clean did not work but following did
eclipse -clean -clearPersistedState
Eclipse often freezes for me at 44% if I'm debugging Android over USB.
When disconnecting the device, Eclipse starts.
The accepted answer allowed me to get Eclipse started again, but it seems that the projects lost their metadata. (E.g., all the Git/Gradle/Spring icons disappeared from the project names.) I have a lot of projects in there, and I didn't want to have to import them all over again.
So here's what worked for me under Kepler. YMMV but I wanted to record this just in case it helps somebody.
Step 1. Temporarily move the .projects file out of the way:
$ cd .metadata/.plugins/org.eclipse.core.resources
$ mv .projects .projects.bak
Step 2. Then start Eclipse. The metadata will be missing, but at least Eclipse starts without getting stuck.
Step 3. Close Eclipse.
Step 4. Revert the .projects.bak file to its original name:
$ mv .projects.bak .projects
Step 5. Restart Eclipse. It may build some stuff, but this time it should get through. (At least it did for me.)
Step1:
Open project directory and edit .project file, remove following lines to disable java script validation.
<buildCommand>
<name>org.eclipse.wst.jsdt.core.javascriptValidator</name>
<arguments>
</arguments>
</buildCommand>
Save file.
Step 2:
Go to Eclipse installed directory and open eclipse.ini(or sts.in if you have STS), change xms and xmx value based on your RAM size of your computer.
-Xms512m
-Xmx1024m
-XX:MaxPermSize=256m
OR: in windows, go to eclipse shortcut in desktop, right click->properties-> add following:
C:\software\eclipse\sts-3.6.2.RELEASE\STS.exe -clean -Xms512m -Xmx1024m
Run Eclipse.
Go to Eclipse->windows->preference->Validation, enable Suspend all validators. Do this if you don't want do any validation listed in the list given in Validator panel.
I have this problem whe I have too much maven projects open at once. What I tend to do is:
Restart eclipse (sometimes I need to kill eclipse)
Disable automatic build immediatly (project > uncheck Build automatically)
Right click the project(s) I want to have rebuild
Close unrelated projects
Re-enable automatic build
This enables a functioning rebuild in 99% off the cases in my workspace.
You may want to take a look at How to report a deadlock. You may also want to check the Error view and/or the error log ([workspace]/.metadata/.log). If that doesn't help, you'll probably need to include more info about which plugins you have installed and which projects you have. Can you create a minimal workspace which reproduces the problem?
I faced Similar issue in Eclipse Indigo. I changed the HeapSize it started working correctly. I just added following eclipse.ini file
-vmargs
-Xms1024m
-Xmx1024m
It worked fine after increasing the VM size
The only solution for me (Luna 4.4.1) was this:
Go to Project Properties > Builders and then uncheck the Javascript Validator.
I had same issue with my Eclipse and as a solution, I created new project, copied all resources manually (using windows copy/paste) to new project, deleted old project and that's it.
Sometimes, this happens due to improper System shutdown and Eclipse workspace started facing similar issues.
Hope it will work.
Unselect automatic build using Eclipse-> Windows->Preferences helps fixing this issue.
Deleting some of the JDT indexes (in .metadata.plugins\org.eclipse.jdt.core), particularly the big files, often fix or ease the problem for me.
I just had the same problem.
By using Task Manager to kill the build process and exiting Eclipse with no projects open, I was able to get back into Eclipse and clean the project without opening it. I then restarted Eclipse again,loaded my project and all OK.
I've found that this might also happen if you rebuild a workspace with a project containing a lot of image data (such as a dedicated images project). Might be best to put something like that into its own workspace and handle it separately to the rest of the projects you deal with.
If you can't, then don't clean that project when you clean and rebuild. Only rebuild when necessary.
In my case problem arise after importing downloaded project - stuck at 80% build. Solved by adding write permissions for group to project's files (Ubuntu 12.04).
In my case it helped to remove the source folders from my favorites in the Windows Explorer (Windows 8.0). It seems that the build was not actually stuck, but triggered in some kind of infinite loop (as mentioned here - Bug 342931).
Sometimes the problem seems to be fixed by killing other programs which have files open from the project folder.
Looking at the logs in [workspace]/.metadata/.log provided useful information for me.
Turned out there was a java.lang.OutOfMemoryError: PermGen space error when the workspace build would hang.
This can be edited in the eclipse.ini or sts.ini(If you are using SpringSource Tool Suite) file.
I faced the same problem when I tried to install Angular.js with bower in my project. I seems bower has lots of javascript files it downloaded automatically which caused my IDE to stuck in validation process for a long time. So, I solved this problem this way,
I first installed tern.js 0.9.0.
Then I went to the project properties, selected tern script path
included only the path I needed for validation, My project's
javascript folder. I excluded other path like placeholders,
Angular.js files, Jquery files.
I selected the Javascript from the properties again and did the same
things in include path's source.
My IDE currently working without freezing. I took help from there. Tern
I guess it can be helpful, where any IDE stuck due to lots of Javascript file.
I tried lots of these suggestions, but the only thing that finally worked for me was creating a new workspace, and freshly checking out all my projects into that folder. Then it worked fine ;-)
I just restarted eclipse and it started working the next time.
Refresh all the projects u want to build.
Worked
Restart eclipse.
It worked for me several times.
I was able to solve this by removing extra folder that Eclipse had created in my eclipse installation folder. I didn't install and I was using Eclilpse Neon 3 with Spring Tool suite also installed. But, when I looked into extracted eclipse installation, I had C: folder which had some folder structure. It was mirror image of my Downloads folder. I removed it and restarted.
It worked for me!
None of the the answers here worked for me. What worked was to delete the following folder
C:\Users\your username\workspace\project
name.metadata.plugins\org.eclipse.core.resources.projects\project
name\.indexes
Rather than debug and find the exact root cause(s) for this, I just deleted the projects and the metadata folder. Eclipse will rebuild the .metadata file the next time it's launched.
I then pulled in the latest project code and the problem was solved. It was more work as I had to reconfigure everything, including my servers, but build workspace had been stopping at 50% for anywhere from 3 to 5 minutes before it would completely finish, so it was worth the effort.
Also, I've found that with Eclipse, if you stop the build workspace before it completes and shut down Eclipse if that hangs up everything, you can really mess up your configuration and waste lots of time trying to get it stable again. I'm using Eclipse Oxygen, but I've had this happen in all the versions of Eclipse I've used, so I really try to avoid it, if possible.
Inside the project folder open .project file. There is a bad entry and it might help
<buildCommand>
<name>org.eclipse.m2e.core.maven2Builder</name>
<arguments>
</arguments>
</buildCommand>
If you are using Maven as a build tool you might want to:
Close eclipse
Delete dependency directories located in .m2/repository/ - in
Linux
it's located under Home directory and in Windows it should be in c:\Users<YourUsername>.m2 (replace '' with your
username)
Start Eclipse and enjoy normal work :)
That helped me resolve this issue and I hope it helps you too. :)
Cheers!
P.S. I've edited my answer (as #howlger asked) where it was also suggested to delete .eclipse and .p2 folders as it can do harm (although it did NOT in my case + I had to reinstall some of plugins I'm using).
In case there is a problem on start when building your project disable the build automatically from menu. Project -> Build Automatically. This solved my problem while more sophisticated solutions could not.