 | Saving to network drive in Eclipse 2 August 2007 16:15 (EST) Working with CFEclipse was never a better time to me until recent days when over time saving network files become slower and slower. Today while saving files (those are on mapped network drive) Eclipse has started randomly throwing error "Save could not be completed. Reason: Has been changed on the file system" after hanging access to network drive for 10-30 seconds and saving an empty file.
It mostly drove me nuts because working with same files through FAR Manager cause no problems at all.
After couple hours of research and play with clean installation of Eclipse, JDK and CFEclipse, JVM performance settings optimization, disabling local antivirus (to scan network drives) and many other tricks, I have discovered Eclipse workspace local history full of garbage.
Every time you modify a file in Eclipse, a copy of the old contents is kept in the local history. At any time, you can compare or replace a file with any older version from the history. Although this is no replacement for a real code repository, it can help you out when you change or delete a file by accident. Local history also has an advantage that it wasn't really designed for: The history can also help you out when your workspace has a catastrophic problem or if you get disk errors that corrupt your workspace files. As a last resort, you can manually browse the local history folder to find copies of the files you lost, which is a bit like using Google's cache to browse Web pages that no longer exist. Each file revision is stored in a separate file with a random file name inside the history folder. FAQ: Where is the workspace local history stored?
So after removing all these history files my Eclipse has started flying again :) Comments Drop a comment... don't be shy
| |
