Rare Null Write Glitch
I was just working on a css file, and I think I hit ctrl+shift+s for a save all, and suddenly the file blanked out, and I quickly found out that it had cleared everything somehow, then saved, or something like that. But the end result: I lost the entire file, no getting it back. I have a backup, but it’s pretty old, I might as well rewrite it all.
If anyone can find the bug that caused this, and save others from the same fate, I’d be grateful.
Unfortunately this is seems to be a not to seldom problem, see e.g.
, but typically that happens in relation with a N++ or OS crash.
I guess this needs to be divided into, at least, two different issues.
One which causes the file to be erased and the other resulting in a NULL-filled file.
If the file is completely empty this could lead to the assumption that the file
was opened and before flushing the content the write operation was interrupted.
Either by os shutdown, process dying etc…
This kind of issue cannot be prevented in a 100% guaranteed way.
The other issue where a file is filled with NULLs is a little bit strange as it is not clear
why this happens at all. I’m suspecting backup functionality but because I haven’t found a
way to prove this it still could mean I’m wrong.
Recently I started investigating what could be done to find out under which circumstance
a file will be filled with NULLs but, unfortunately, haven’t yet found a secure way for monitoring
rare null write
suddenly the file blanked out,
cleared everything somehow
What is “null write”, “blanked out”, “cleared everything”? Such a serious thing deserves a better bug report if it is to get addressed.
And a backup that is “pretty old” is no backup at all. That’s on you, not Notepad++.
Sorry to be brutal…facts are facts.
@Claudia-Frank To be clear, the file became 0kb. It literally has nothing int it.
@Alan-Kilborn I realize having only an old backup is my fault. I assure you, I won’t be making that mistake twice.
The current file blanked out while I was looking at it when I tried to save all, so it’s definitely notepad++'s fault.
may I ask, you used save all to save all open files or just save to save the current file or
you used save all but only one file was opened at that time?
If you used save all for all open files, were additional files affected or only this one?
Btw. do you use npp’s backup functionality and if so, what is the configuration?
@Claudia-Frank I had two files opened, css file was the one deleted, and an html file on the tab to the right, which was unaffected.
I use the plugins Autosave and Autosave 2, but only after this happened, no other backup functionality is set up.
… and you used save all or just save in this case?
Was there anything to save for the html file or was it not modified at that time.
Btw. could you post the debug-info? (available under ? menu)
I use the plugins Autosave and Autosave 2
Maybe it is Autosave’s fault…somehow…?
Saving right at the instant the user does…maybe an interaction?
Just a thought…
@Claudia-Frank Notepad++ v7.5.3 (32-bit)
Build time : Dec 5 2017 - 10:45:46
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 7 (32-bit)
Plugins : AutoSave.dll autosave2.dll DSpellCheck.dll mimeTools.dll NppConverter.dll NppExport.dll NppFTP.dll PluginManager.dll
I used save all, the html file likely hadn’t been modified recently.
By the way, this happened before updating, I think I was in 7.4. I think it’s worth noting that the 7.4.1 release log says “The opened zero length file not saving bug.” was found, possibly related.
@Scott-Sumner I didn’t have those plugins installed at the time.
Just to summarize what happened
Npp most likely version 7.4
Using no npp backup functionality and no plugins which do backup files at that time.
When pressing save all the entire current active file got erased, other files weren’t
affected although it might be that other files haven’t had any modification at that time.
Npp kept running - no crash or npp restart.