Haven't tested on windows but I've found under linux that a file open for editing in theide will be overwritten with junk if you have a spontaneous reboot or particularly bad app crash.

I suppose what I'm getting at is this: if you write a bad application and run it does theide fork a child process that could access the parent's memory (in this case, the currently open file) and overwrite it with junk which would then be written to the filesystem once theide has focus again?

I get what you're saying. I suppose I should be clearer myself. We agree that the file's likely not open... but the file's data is still in the editor. And you said the file is saved when focus changes. Well running the app would change the focus, causing a save, would it not?

I suppose it's not worth arguing if as you say it's not forked with memory sharing, but the scenario I was describing:

* you run badapp
* new child process is created, it shares memory with theide
* child process is badly behaved and modifies parent memory (by that, I mean it changes the text in the editor itself, the array backing it, not any open file)
* theide sees the focus has changed to the new process, opens the file and saves the mangled contents of the editor back to the file

So all I meant to suggest is that the contents of the editor are being overwritten, not the file directly.