https://bz.apache.org/ooo/show_bug.cgi?id=126990
--- Comment #16 from John <[email protected]> --- See "Text in document transformed to #####" at https://forum.openoffice.org/en/forum/viewtopic.php?f=7&t=104676#p507553 where a user describes exactly what happened to cause a .odt file to become full of #####. > The piece of writing that I have lost is an OpenDocument Text [ie a .odt > file]. > > I opened it and had been working on it for few hours, saving it > every 10 minutes or so, when my computer froze and showed a grey screen. > As this hadn't shifted despite my best efforts I had to do a forced shut > down after about half an hour. > > When I restarted the computer it was all fine apart from the document > I had open on the screen where the text had been replaced by ###### > > [ie - when AOO opened ...\fred.odt, the file displayed as ##### > which means ...\fred.odt was a flat file (not a ZIP container) full > of null characters. Inspection of ...\fred.odt uploaded to the forum > shows fred.odt is full of null characters As I understand it, when AOO edits fred.odt: 1. AOO copies ...\fred.odt to a temporary file in ...\Temp. 2. AOO marks ...\fred.odt as "in use". If I send ...\fred.odt to 7-ZIP I get a 7-ZIP error message "The process cannot access the file it is being used by another process". However, I can copy the file and I can send the file to Notepad++ where it opens. 3. All user changes are held in memory until the file is saved. ...\fred.odt is thus never touched until a Save is done. 4. When a Save is done, ...\fred.odt is saved as a proper .odt file. As the user saved the document I would expect ...\fred.odt to be a proper .odt file containing the document exactly as it was when the document being edited was last saved. So why is ...\fred.odt a flat file full of nulls when the PC is restarted? Could it be that AOO was writing a Save when the PC froze - indeed, AOO probably caused the freeze. In this case, I would expect ...\fred.odt to be as it was when the PC froze and this is why it is full of nulls. So, is there a stage during the file write process when ...\fred.odt is set to be full of nulls? Or some Windows process that kicks in as a freeze happens which fills the file full of nulls? -- You are receiving this mail because: You are the assignee for the issue.
