|Again seeing Eclipse workspace corruption on a VM [message #1741189]
||Tue, 23 August 2016 15:23
| David M. Karr
Registered: July 2009
Last year I posted a bug about frequent workspace corruptions running Eclipse in a VM on my laptop: https://bugs.eclipse.org/bugs/show_bug.cgi?id=482735 .|
This morning I saw another workspace corruption on my VM. What's changed? Quite a lot. I'm on a different laptop, different laptop and VM OS, different SCM (SVN vs. git) and a completely different (and much smaller) set of projects in my workspace. There also is no shared drive in the mix here, so everything about this is simpler than before.
My Eclipse log file has quite a few exceptions, but I think it's pretty likely they are just a symptom of the workspace being corrupted (NullPointerExceptions, for instance).
I tried going into the Oomph preferences tolook for something to repair. There appeared to be one item that was eligible for repair, but restarting after that made no difference.
Is there anything else I can try before I create another workspace and reimport (and copy) everything again?
Just so it's clear, by "corruption", I mean that instead of listing my projects in the Package Explorer, it just shows "RemoteSystemsTempFiles". In the editor view, it sort of restored the last files I was editing. It has the file names, but the contents are empty, since it thinks it can't find those files. If I browse the workspace through the file system, the projects I had look perfectly fine. I can even build them successfully from the command line.
[Updated on: Tue, 23 August 2016 15:34]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02416 seconds