Slightly adjusted version of a Dilbert strip:
Boss: I want you to create an artificial intelligence that is as smart as me.
Engineer: OK.
Ten minutes pass.
Engineer: Done.
Boss: Wow, you’re fast.
Engineer: … Yes.
Slightly adjusted version of a Dilbert strip:
Boss: I want you to create an artificial intelligence that is as smart as me.
Engineer: OK.
Ten minutes pass.
Engineer: Done.
Boss: Wow, you’re fast.
Engineer: … Yes.
In this article, I’m trying to collect the steps to find out the reason when Eclipse is suddenly slow:
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:
org.eclipse.ui/debug=true org.eclipse.ui/trace/graphics=true
If the m2e plugin causes problems:
WORKSPACE_ROOT/.metadata/.plugins/org.eclipse.m2e.logback.configuration