Community
Participate
Working Groups
Build Identifier: I20100603-1500 Eclipse cannot get past the splash screen, hangs at the "Loading Workbench" state. The only filesystem activity is accessing the .metadata\.plugins\org.eclipse.dltk.core.index.sql.h2\model.lock.db file. .log file is: !SESSION 2010-06-22 16:52:34.978 ----------------------------------------------- eclipse.buildId=I20100603-1500 java.version=1.6.0_18 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pl_PL Framework arguments: -product org.eclipse.epp.package.php.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.php.product !ENTRY org.eclipse.core.resources 2 10035 2010-06-22 16:52:39.335 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. Reproducible: Always Steps to Reproduce: 1. Run eclipse 2. Choose a workspace 3. Eclipse starts loading workspace then hangs.
Created attachment 172422 [details] Loading Workbench hangs
Created attachment 172423 [details] PRocess activity while in the hang state.
I have a second (backup) workspace, which works just fine. The first one (original) cannot load. I tried the "-clean" command line option but it does not help.
> !ENTRY org.eclipse.core.resources 2 10035 2010-06-22 16:52:39.335 > !MESSAGE The workspace exited with unsaved changes in the previous session; > refreshing workspace to recover changes. I guess the workspace might be corrupted due to an earlier crash. Does it hangs in a fresh workspace also?
Removing the .metadata folder and restarting eclipse works , but this is not a solution since the workbench gets wiped out.
I am experiencing this in 3.5.2 , and it happened several times.
I created an empty workspace from scratch and it seems to work, but problem , however , remains. Is there any way to reclaim the workspace settings ? Is there any way to increase the verbosity of eclipse so that we know what kind of "workspace corruption" it is ?
(In reply to comment #7) > Is there any way to reclaim the workspace settings ? Well, the settings are stored in your .metadata folder. If you have destroyed it then you're not going to get them back. > Is there any way to increase the verbosity of eclipse so that we know what kind > of "workspace corruption" it is ? Not exactly. If a process appears to be hung, you should try to get a thread dump.
(In reply to comment #8) > (In reply to comment #7) > > Is there any way to reclaim the workspace settings ? > > Well, the settings are stored in your .metadata folder. If you have destroyed > it then you're not going to get them back. It's not that I destroyed it on purpose, It was eclipse that crashed :) > > > Is there any way to increase the verbosity of eclipse so that we know what kind > > of "workspace corruption" it is ? > > Not exactly. If a process appears to be hung, you should try to get a thread > dump. I know that my suggestion may be beyond the scope of this ticket but it would be nice to have some kind of workspace data pre-check before it gets loaded and hangs the application...
(In reply to comment #9) > > Well, the settings are stored in your .metadata folder. If you have destroyed > > it then you're not going to get them back. > > It's not that I destroyed it on purpose, It was eclipse that crashed :) What I mean to say is, did you just delete the .metadata folder, or did you just rename it/move it out of the way? Though, based on your response, it sounds like you deleted it.
(In reply to comment #10) > (In reply to comment #9) > > > Well, the settings are stored in your .metadata folder. If you have destroyed > > > it then you're not going to get them back. > > > > It's not that I destroyed it on purpose, It was eclipse that crashed :) > > What I mean to say is, did you just delete the .metadata folder, or did you > just rename it/move it out of the way? Though, based on your response, it > sounds like you deleted it. I did not touch the "corrupted" workspace nor the .metadata folder inside. It stays intact awaiting further analysis :) To get my projects going I simply created _new_ workspace from scratch, with new .metadata folder inside, and imported all projects from the "corrupted" workspace. Thus, I have now two workspaces now: 1) Corrupted workspace which I am unable to use (eclipse hangs)- preserved intact for further analysis. 2) New workspace which works fine.
(In reply to comment #11) > I did not touch the "corrupted" workspace nor the .metadata folder inside. > It stays intact awaiting further analysis :) If it is still there then you may be able to get around the problem by moving/renaming/deleting the .metadata/.plugins/org.eclipse.core.resources/ folder. You will be forced to re-import the projects so that Eclipse will become aware of them.
Here is how you can generate a thread dump at the time Eclipse is hung. Please attach the thread dump file to this bug so that we can investigate further: http://wiki.eclipse.org/How_to_report_a_deadlock
Need a thread dump before we can look at this further. Please reopen if you can provide that.
