https://issues.apache.org/ooo/show_bug.cgi?id=118725
Matthias Basler <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #13 from Matthias Basler <[email protected]> --- I can now confirm the bug on AOO 4.1.0, albeit with a larger sample. Tried to reproduce this behaviour with a scrambled book of 165 pages with ~1 image per page. Memory consumption is huge ... ~1.5GB, and after I add another image I am hardly able to "Save as" the document. Opening the dialog takes forever and pressing "Save" does ... absolutely nothing. ... Correction ... After another 2 minutes and several presses it finally reacts. :-( So I save the file into a DIFFERENT directoy. Memory consumption drops to 100MB. Strange - why does it suddenly need less? I add another picture. Then again I save the file into a DIFFERENT directoy. This time AOO is more responsive. After every image I insert into the doc AOO jumps to the end of the document. What the hell ... ? And then there they are when I scroll through the document: The boxes saying "Lesefehler" ("Read error") where images used to be. A document devoid of almost any images is what is left. As usual, since the file is far too big (140MB, sigh ...) I'll upload it in my GMX MediaCenter. But please be warned: IT WILL NOT STAY THERE FOREVER EITHER! Please use the file "TestBook2.odt" there for this issue. https://mc.gmx.net/guest?path=Meine%20Dokumente%20von%20matthiasbasler%40earthflight.org&token=425CD698469014B4&locale=de_DE&viewType=0 I also tried another, slighly smaller test document, but with that AOO instantly crashes on loading. :-( I believe I am wasting my time here trying to avoid other bugs just to test one. Remarks: 1. If I remember correctly LibO fixed this bug a while ago. (See the meta bug mentioned above.) 2. "image caching / management is utterly shambolic" really hits the point. 3. I am pretty sure - although not 100% - that this is the same effect as described by Chnutz. Same sequence of saving and image loss. 4. Oh, and I believe this makes the issue CONFIRMED again, doesn't it? -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue. You are watching all issue changes.
