Page 1 of 1
Loading Eclipse fails at Loading Workbench
Posted: Sun Aug 08, 2010 9:53 pm
by v8dave
Hi all,
I am getting an issue when trying to load Eclipse. It was working last week and no new software has been installed.
It hangs at the splash screen showing "Loading Workbench" and Task Manager show it as not responding. There is no disk activity other than normal.
Any ideas?
Dave...
Re: Loading Eclipse fails at Loading Workbench
Posted: Mon Aug 09, 2010 3:30 am
by v8dave
Couldn't get it to work even after checking the XML file so uninstalled, moved the projects and then reinstalled and imported them back in and now it is working again! Bit of a headache but at least I am working again.
No idea what happened but now when I am done I am backing up the workspace directory even though I check code into the repository each day, the Eclipse setting do not get saved.
Dave...
Re: Loading Eclipse fails at Loading Workbench
Posted: Mon Aug 09, 2010 10:23 am
by Forrest
Are you sure the "Select Workspace" window was not buried behind other windows, or minimized? That has happened to me before.
Re: Loading Eclipse fails at Loading Workbench
Posted: Mon Aug 09, 2010 12:33 pm
by tod
Too bad I'm too late with a response. There is a -clean option when booting Eclipse that cleans up your .metadata folder. It would be interesting to know if that worked. Maybe next time. There's a
good blog on keeping Eclipse clean for future reference. I don't include my .metadata folder in subversion. I thought about it, but its 200 MB, changes all the time and Eclipse is supposed to be able to rebuild it if needed.
Re: Loading Eclipse fails at Loading Workbench
Posted: Mon Aug 09, 2010 7:16 pm
by v8dave
Hi Tod, thanks for the info for future use. If it happens again, I will give it a try.
Forrest, at first this is what I thought as I have been getting strange dialog issues on this machine of late but there was nothing. Task Manager was showing it as not running so I suspect something internal had crashed. I found that there is a log file but sometimes this was not always being written to but it did point me to the workspace as the culprit from an earlier error which had been written out.
Dave...