In this article, I’m trying to collect the steps to find out the reason when Eclipse is suddenly slow:
- Java GC. To find out if that’s the culprit, go to Window -> Preferences -> General and enable “Show heap status”. You will get a little gauge at the bottom of the Window. If the gauge is almost full, then you probably have too little memory.
a) Give Eclipse more memory
b) Close some projects
c) Deinstall or disable unnecessary plugins
- Check the Eclipse Error Log. Maybe there is a problem under the hood.
- Some plugin is acting up. Enable Eclipse’s own logging (see below) and watch the console.
Some plugins have their own console (Groovy, Maven). In the Console View, click the arrow of the “Open Console” button to get a list. The Stacktrace Console – a useful tool to examine stacktraces from some external source – is also hidden there.
- The metadata got corrupted. Clean it.
Enable Eclipse’s Console Logging
When you start a Java application inside of Eclipse, you can see the output in a console view. You can do the same for Eclipse itself.
Open eclipse.ini and add these lines right before -vm (or -vmargs, if there is no -vm line):
-console -consoleLog -debug
See “Debug Mode“, “Eclipse runtime options” and “FAQ How do I use the platform debug tracing facility”
On Windows, make sure Eclipse is started with java.exe instead of javaw.exe.
Eclipse will log errors and trace information to the console window. Check the output.
Many Eclipse plugins offer a range of trace options. You can see them if you open the plugin JARs. Look for a file called “.options”.
If you copy some of those into a file “.options” in the same folder as “eclipse.ini”, you can able various logging options.
Here is an example what the file could look like:
Maven m2e Plugin
If the m2e plugin causes problems:
- Look into the Maven console.
- Try Maven from the command line to see whether it’s a problem with the project in general or with m2e.
- Tweak the logging options of m2e by editing