| corrupt workspace - help [message #201058] |
Thu, 22 March 2007 13:14  |
Eclipse User |
|
|
|
Originally posted by: francisco.x-hive.com
Hello,
Eclipse crashed with a out of memory error, and now my workspace is corrupt.
If I try to restart Eclipse, it remains eating all CPU it can, and anything
I try to do will give an "user operation is waiting for background work to
complete". Trying to exit Eclipse without killing it, also does not work.
If I try to restart using Eclipse 3.2.2, I get this on the log file:
!SESSION 2007-03-22
13:26:09.957 -----------------------------------------------
eclipse.buildId=M20070212-1330
java.version=1.6.0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86
!ENTRY org.eclipse.core.resources 2 10035 2007-03-22 13:26:13.473
!MESSAGE A workspace crash was detected. The previous session did not exit
normally.
!ENTRY org.eclipse.ui 4 4 2007-03-22 13:26:16.986
!MESSAGE Unable to find extension: org.eclipse.ui.presentations.33 in
extension point: presentationFactories
====================================================
If I try to restart using 3.3M5eh, I get a message "Initializing Java
Tooling", Eclipse remains eating all CPU,
!SESSION 2007-03-22
13:29:39.734 -----------------------------------------------
eclipse.buildId=I20070222-0951
java.version=1.6.0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework
arguments: -launcher /home/borges/local/packages/eclipse/3.3M5eh/eclipse -name
Eclipse -start
Command-line arguments: -os linux -ws gtk -arch
x86 -launcher /home/borges/local/packages/eclipse/3.3M5
!ENTRY org.eclipse.core.resources 2 10035 2007-03-22 13:29:41.685
!MESSAGE A workspace crash was detected. The previous session did not exit
normally.
[...]
Anyone knows how to deal with this? Tips? Hints?
In the mean time I guess I should just go on re-creating the workspace....
:-/
Cheers,
Francisco Borges
|
|
|
| Re: corrupt workspace - help [message #201085 is a reply to message #201058] |
Thu, 22 March 2007 14:47  |
| Eclipse User |
|
|
|
Originally posted by: bschilke.biz.gmail.com
Maybe you can compare the folders and meta-file(s) between your new
workspace and the old corrupt one? It might help narrow down the issue.
|
|
|
|
| Re: corrupt workspace - help [message #201360 is a reply to message #201165] |
Fri, 23 March 2007 09:19 |
| Eclipse User |
|
|
|
Originally posted by: francisco.x-hive.com
Paul Rubin wrote:
> Francisco Borges wrote:
>> Hello,
>>
>> Eclipse crashed with a out of memory error, and now my workspace is
>> corrupt. If I try to restart Eclipse, it remains eating all CPU it can,
>> and anything I try to do will give an "user operation is waiting for
>> background work to complete". Trying to exit Eclipse without killing it,
>> also does not work.
>>
>
> Does starting Eclipse with -clean help?
No, that didn't help at all. Also tried "-refresh", FWIW, but didn't help as
well.
I've also tried to restore the workspace with
this "org.eclipse.core.tools.restorer_1.0.0.zip", but it also didn't save
the day.
[...]
I really would rather Eclipse not to rely so much on saved state
information, or to be able to use the last "cleanly saved state", when
finding a corrupt wokspace.
In the mean time, I just re-created the workspace :-\
Cheers,
Francisco
|
|
|
| Re: corrupt workspace - help [message #201591 is a reply to message #201360] |
Sun, 25 March 2007 00:39 |
| Eclipse User |
|
|
|
Originally posted by: eclipse5.rizzoweb.com
Francisco Borges wrote:
> I really would rather Eclipse not to rely so much on saved state
> information, or to be able to use the last "cleanly saved state", when
> finding a corrupt wokspace.
Actually, Eclipse has almost no reliance on state that can not be
recreated upon restart. It is purposefully designed to make its writes
to disk as quick and atomic as possible and to be able to re-generate
whatever it needs if it can't find it.
That being said, there are always going to be places in the code, no
matter how tiny, where critical data writing can potentially be
interrupted by a JVM crash. Even so, in the 5 years I've been using
Eclipse on a daily basis it has only corrupted a workspace a couple of
times for me (and that was back in the version 2 era).
By the way, before creating a whole new workspace it is often enough to
simply delete parts (or all) of the .metadata directory - that is the
only place where corrupt data could be stored.
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.08363 seconds
] 
Search
Help
Register
Login
Home
