https://bugs.freedesktop.org/show_bug.cgi?id=39930
--- Comment #6 from Bill Gradwohl <[email protected]> 2011-09-25 14:26:12 PDT --- (In reply to comment #5) > Did you ever experience any difference with different versions of LibreOffice > (OpenOffice)? This problem was only discovered under LO, but that's only because the machine used is Fedora 15 with LO. I don't have another similar machine running OO to test with. > Do you think there is a stripped down version thinkable that would help to > analyse the source of trouble? No. This spreadsheet, when broken, is so sensitive to any changes that trying to strip it down is impossible. Try deleting one of the T1 to T10 sheets to see what I mean. Usually, doing so appears to work just fine, as the spreadsheet continues to function normally, but a save and reload fails due to corruption. Just moving a sheet from one position to another appears to work, but a save and reload usually fails. I've used this spreadsheet for several years in our business. When it starts to go bad, it does all sorts of strange things, and by then it is too sensitive to touch to try to strip it down. I'm a professional software developer. I spent 30 years writing code on mainframes and PC's. That experience tells me that, although I haven't looked at the source code, the problem is with OO's writing of the xml file. OO/LO writes a file (save) that it can't read the next day, or reads and then misinterprets what it read. On numerous occasions the last save of the day produced a file that couldn't be opened the next day due to file corruption, even though the spreadsheet ran fine up to the last save of the day. Someone needs to seriously look at the conversion from what the spreadsheet looks like in memory to a version represented in xml. I'm convinced that's where the problems are injected. Due to the backup system I wrote specifically to track this problem, I have dozens to hundreds of versions of this spreadsheet as it evolves during a day of use. Analysing those copies has shown huge sections of rubbish that when I remove it, produces a file that will again at least load, and sometimes also function as expected. How did that rubbish get into the file?? Obviously, LO put it there by misinterpreting what was in operating RAM at the time. That's how buttons shrink - by misinterpreting something and writing out the xml of the misinterpretation. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
