Menu
After selecting the workspace, eclipse takes about 10 minutes to initialize? What could be the problem?
671
In development, when you find the eclipse workspace build process is slower and slower, and if the main reason is because of validating static files ( for example validate JS, CSS, XML file, and so on). Then you need to reduce or remove the validators in the eclipse preference validation section.
In your eclipse. ini file (inside eclipse installation folder) change the default -Xms40m -Xmx256m arguments as per your needs. This option defines the minimum and maximum memory usage bounds which are passed to java virtual memory to manage eclipse application's memory allocation tolerance.
The issue you are experiencing may be tied to the active provider in Eclipse's Network Connections settings: Direct - "Choosing the Direct provider causes all the connections to be opened without the use of a proxy server." Manual - "Selecting Manual causes settings defined in Eclipse to be used."
Eclipse shouldn't take this long to initialize unless you have a lot of plugins (especially buggy ones) installed. Do you get the slowdown after the workbench is already shown? That could indicate a plugin.
You may want to verify with your Eclipse installation how much max heap it is allocated. Eclipse traditionally ships with a very low default for modern machines. If you are on Windows, look at eclipse.ini in your Eclipse directory and change the -Xmx parameter to something meaningful (e.g., 2048M)
70
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
