>>Answering Jeff's questions from last week. As an update, I came back after a week outside my office and lo and behold, the problem disappeared. I had also switched off and restarted my computer when I came back. I am not able to reproduce this saving problem now. But this has happened to me more than once, so next time I run into the problem, I will run the profiler and look in the log file as well. Answers to other questions are below...
> Later yesterday, I had refactoring turned off, but a Ctrl+S to save took
> about 1.5 minutes (I counted!). And the CPU usage monitored on?TOP jumped to
> 100% for the entire 1.5 minutes. ?Any idea why that would be?? And there was
> no progress bar at this point.
I've never seen this before. It's odd that amount of time needed to
save a file would increase over time. A few questions, if you don't
mind...
1. How big is the file (lines of code and/or total bytes)?
>>The files have about 1100 lines in them
2. Is your workspace stored on network drive/NFS? This is not a
remote project (using RSE or RDT), right?
>>No it is stored locally.
3. Do you have plug-ins for Subversion, Git, or other version control
systems installed?
>>Yes, I do have Subversion installed
4. Try checking the box "Show Heap Status" in Window > Preferences >
General. This will put a heap monitor in the status bar on the lower
right-hand corner of the workbench. What sort of numbers is it
reporting? Does it escalate or oscillate during the save?
5. Try opening the file in an ordinary text editor (right-click > Open
With > Text Editor), making a similar change, and saving it. Does it
still take that long to save, or only in the Fortran editor?
>>Only in the photran editor. Using Vi or Vim, outside of eclipse did not make a difference. I will check to see if opening a different editor within eclipse makes a difference (see answer below as well)
6. Would you mind sending me the
/path/to/your/workspace/.metadata/.log file? If there's an exception
being thrown, it ought to be logged there.
To answer your question, yes, the Eclipse platform keeps a local
history of each file, although I wouldn't expect that to slow things
down... unless it's storing a massive history on a network drive, or
something like that...
>>Where would such a file be stored? Is there a way to clean this history file, or change how much history is stored?
Thanks,
Anusha
