Bug 64468 - Dirty editor is not admitting that it has changed
Summary: Dirty editor is not admitting that it has changed
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 RC2   Edit
Assignee: Tom Hofmann CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2004-05-27 18:22 EDT by Carolyn MacLeod CLA
Modified: 2007-06-22 10:04 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carolyn MacLeod CLA 2004-05-27 18:22:58 EDT
Build 200405270800 of eclipse.
Something is really messed up somewhere with the dirty flag.
This was not happening in 20040525 but it has happened twice for me in 
200405270800.

The symptoms (which seem to be all related) are:
- I replaced with previous, and got the "File has changed on disk" dialog when 
I clicked on an editor that was already open. (This happened the first time I 
did a "replace with HEAD" in 2 different workspaces).

- I refreshed (even though I shouldn't have needed to) and then edited the 
file, and after saving, my '>' label decoration does *not* show up, even 
though CVS label decorations are enabled. Also, "Revert file" on the context 
menu is not enabled.

- Synchronize is not picking up the changes either.

- If I browse changes with another revision, and select the currently loaded 
revision, the comparison viewer doesn't show the newly typed contents of the 
file. It is very strange. The changes are there - I can see them when I look 
at the file - but none of the other viewers can see them, and nobody thinks 
the editor is dirty.

- I deleted the editor and reopened it, and all seems ok now.

So it looks like it is possible to get into a state where an editor doesn't 
think it belongs in the IDE (if I can put it that way). This is very strange 
and very disconcerting, and it feels like a really bad problem until you 
stumble on the work-around. I will try to replicate it, but maybe it has to do 
with using 200405270800 with an existing workspace - not sure.
Comment 1 Carolyn MacLeod CLA 2004-05-27 18:24:27 EDT
Oops - I forgot to finish typing the summary...
Comment 2 Carolyn MacLeod CLA 2004-05-27 18:48:39 EDT
This happened to me again - it's *really* bad. I would say that it is P1 for 
3.0. Here's what I did:
1) Downloaded 200405270800.
2) Started eclipse on an existing workspace.
3) Opened a file (org.eclipse.swt.widgets.Combo.java) that I knew had new 
changes on the server that were not in my workspace.
4) Selected the containing project (org.eclipse.swt) and said "Replace with 
latest from HEAD". The replace happened without incident.
5) Then, I clicked on the Combo.java editor, and I was greeted with a dialog 
that says "The file has been changed on the file system. Do you want to load 
the changes? Yes/No".
6) Of course, neither Yes nor No makes any sense, since this is a completely 
bogus dialog, however I had to choose something, so I said "No".

I am now in a state where I have an editor in no-man's land. I can type space 
and there is no indication of dirty (i.e. the * in the editor's title is not 
displayed). Revert file and Save are both disabled. This editor is toast, and 
the only thing I can think of to get back to a normal state is to delete it, 
and open a new editor on Combo.java.
Comment 3 Kai-Uwe Maetzel CLA 2004-05-28 04:45:30 EDT
To be investigated. As we are posting runnables for checking the state of the 
editor's input file, late changes in the progress world could have affected us.
Comment 4 Silenio Quarti CLA 2004-05-28 19:40:09 EDT
This happens quite often to me on GTK and Motif. It might be related with 
editing in the CVS compare/synchronize view.
Comment 5 Tom Hofmann CLA 2004-06-09 06:39:46 EDT
investigating
Comment 6 Tom Hofmann CLA 2004-06-09 12:06:46 EDT
I cannot reproduce the scenario described in comment 2 on I20040609. Carolyn and
Silenio, are you still seeing this? Are there any other scenarios that you can
consistently reproduce? Closing as remind, please reopen with more information.
Comment 7 Dani Megert CLA 2005-05-24 09:27:47 EDT
I guess you run into bug 96336, which contains steps to reproduce this.
Comment 8 Dani Megert CLA 2007-06-22 09:59:00 EDT
Get rid of deprecated state.
Comment 9 Dani Megert CLA 2007-06-22 10:04:20 EDT
.