https://issues.apache.org/ooo/show_bug.cgi?id=59915
Joe Smith <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #41 from Joe Smith <[email protected]> --- I have an alternative scenario to demonstrate the problem--the symptoms of the problem at least. What I've done is to configure OO to use a temp file location that has limited space: The open document (33 embedded images) occupies about 30Mb in temp files The limited temp area has ~15-20Mb available There's enough temp space for the main document components but not enough for all the images. In this situation, OO appears to open the document cleanly, except that some of the images have the "Read error" place holder. If I try to save the document in this state (no more temp space), I get "General i/o error ... Can't save subdocument content.xml". If I then free up some temp space and save again, no error occurs and the resulting file has simply lost some of the images. I expect that running out of disk space is unlikely to happen for current systems with large disks. But even if this is not the actual cause of the problem, I think this does demonstrate a flaw in the design of OO, that a serious, document-damaging error is not brought to the user's attention, allowing the document to be permanently damaged. I believe this could be related to the image caching: it seems that OO may not effectively deal with errors in managing the cached files. Errors in unpacking any part of the document archive (write error: no space in this situation) should be fatal errors--the document should not open. -- You are receiving this mail because: You are on the CC list for the issue. You are watching all issue changes.
