[Mike Cico]

After a craash, or if eclipse gets deadlocked, when I restart it can take upwards of 1/2 an hour to restart it. I’ve removed the .lock file, but it seems like its doing some kind of rescanning of things in such situations.

It doesn’t lock the CPU or anything, but it just takes forever. I’m not sure if it’s spinning at a low-frequency, or if it’s waiting on some other lock file in the workspace, or whatever.

I’m using MyEclipse 4.0m2, on the GA release of Eclipse 3.1. But, this happened with earlier versions of Eclipse as well. It seems like it’s a general eclipse issue, not necessarilya MyEclipse issue.

Thanks,

Mike Cico

[Brian Fernandes]

Mike, that is an enormous amount of time to start Eclipse.

How are you starting eclipse, do you use any command line parameters?

Please state your OS and JDK versions as well.

Best,
Brian.

[Mike Cico]

Here’s my shortcut args:

C:\eclipse3.1\eclipse\eclipse.exe -vmargs -Xmx512M -Dosgi.splashLocation=”C:\Program Files\MyEclipse40For31\MyEclipseSplash.bmp”

Again, it only seems to happen after a crash, or if it gets hung and I have to kill it and restart it. It’s something I had an issue with in 3.0.x as well. What’s a good debug switch to turn on so I can track what’s happening during startup?

[Brian Fernandes]

Mke,

You forgot to mention your OS and JDK.

I don’t know what to make of the issue yet, do you have many / large projects in your workspace and is Build Automatically turned on (it usually is)…

What happens just before the crash, is there a common reason due to which it crashes? Try adding the -clean switch to the shortcut just once (remove it for subsequet runs), that could help clear things up.

Let us know how things turn out,

Best,
Brian.

[Scott Anderson]

Mike,

Eclipse might be thrashing around trying to recover the workbench state from the large number of cached config files it keeps. There’s really no way to know. However, the next time it crashes, I’d try restarting it by adding the -clean option (eclipse.exe -clean …) to see if just telling it to rebuild the plugin cache and not worry about what’s already there will speed things up.

[Mike Cico]

OS is WinXP, using JDK 1.5_03

It rarely actually crashes, usually it gets hung up doing that makes me have to kill it…the “something” I haven’t isolated yet.

I do have one really large project. In general, I and my co-workers have found that the initial rampup of a new project with a large src base is very time consuming with Eclipse in general. I’ve found that it’s best to create an empty project and create the source path later where I can add the proper includes/excludes, etc.

But, once the intial setup is done, and the initial Type indexing is done, Eclipse is very responsive, and quick to start up.

And no, re-organizing the src area is *not* an option ;-).

Thanks guys, I’ll try to use the -clean option next time I have to kill and restart…

Mike

[Scott Anderson]

Mike,

One other thing that helps in general is to close any projects you’re not actively developing. That makes them ‘invisible” to Eclipse so they won’t get rebuilt during a workspace rebuild. So, if you’ve got a bit project that you rarely work on, it might make sense.

[Author]

Posts