https://bz.apache.org/ooo/show_bug.cgi?id=126970
--- Comment #20 from John <[email protected]> --- Created attachment 85549 --> https://bz.apache.org/ooo/attachment.cgi?id=85549&action=edit Screen dump of images while AutoSave is taking place, and immediately after Amazingly, I now have a file where the image loss is reproduceable every time I open the file. I have uploaded 0 June_MASTER v2 AJB.odt to https://www.dropbox.com/s/n3zgrpx5l1s2jx1/0%20June_MASTER%20v2%20AJB.odt?dl=0. I have also saved my complete profile (140 MB) and can upload it if required. Images are lost on - my desktop and my wife's laptop (both Windows 10 Home, 64 bit, AOO412m3(Build:9782) - Rev. 1709696 2015-10-21 09:53:29 (Mi, 21 Okt 2015)) - a laptop (Windows 10 Home 64 bit, AOO 4.1.2 as above) - RoryOF's Xubuntu 16.04 64 bit, AOO 4.1.2 - acknak's Fedora release 23 (with /opt/aoodev/AOO412rc3/openoffice4/program/soffice -h OpenOffice 4.1.2 412m3(Build:9782) and $ cat /etc/redhat-release Fedora release 23 (Twenty Three) History: I created the file using AOO to create a Master document. I exported the Master and sub docs to a .odt to send to my proofreader so that his changes could be recorded. He uses LibreOffice, and he recorded changes in the .odt, and returned the file to me. The repeatable every time sequence to lose images is as follows: First, I have these settings: a) Tools > Options > OpenOffice > Memory ... - set Remove [graphics images] from memory = 1 minute b) Tools > Options > Load/Save ... - Tick Always create backup copy. - Tick AutoSave and set to 2 minutes. 1 Close all AOO documents etc. Close AOO. I don't use quickstart, so close quickstart just in case. 2 Open 0 June_MASTER v2 AJB.odt by double clicking it. - Say NO to update links. - Format > Sections > Select all > untick Link. Note how unlinking causes the Save icon to go dark - this starts the 2 minutes clock for AutoSave as you have changed the document. 3 Slowly scroll down until you see an image or two on screen. Now do nothing - just wait ... But keep the Writer window as the active window with the mouse in it. 4 Observe what happens when the AutoSave takes place after 2 minutes - you will know because the blue dashed bar crosses the bottom of the screen. I lose the images after the blue bar finishes - see attached image of screen shot taken during AutoSave (bar 75% across screen - images present) and immediately after AutoSave (images gone). Analysis shows that when I scroll, each image is written to ...\Temp when the image appears on the screen, irrespective of the graphics flush time. So, if I scroll such that only the first two images appear on the screen, these two, and only these two, images have temporary files written to ...\Temp. But when AutoSave takes place, I lose ALL images in the document, these two and all the others. After the AutoSave, all the other images are written to ...\Temp. Note how this is "Scenario 2 - Writer loses contact with images even though the image temporary files are still in the ...\Temp folder". Other analyses: 1 It does not happen with LO Version: 5.0.5.2 Build ID: 55b006a02d247b5f7215fc6ea0fde844b30035b3 Locale: en-GB (en_GB) 2 Making a slight change to the .odt file prevents its happening! I wanted to anonymise the phone numbers so I used Find and Replace to replace all digits by n. Images were then not lost by doing steps 1 - 4 above. 3 When I scroll DOWN after image loss, I get 4 x Read Error messages boxes (which are blank) for each image. When I then scroll UP, each Read Error message box contains the text immediately below where the image was. This is reproduceable as I coninue to scroll up and down. 4 RoryOF (Ubuntu) reports that he set AutoSave to 20 minutes. He then opened the file as above ... and just left it. After 15 minutes, the images were lost. 5 I repeated Rory's test by setting AutoSave to 40 minutes and leaving the file. My images were present at 35 minutes, but were lost after the AutoSave at 40 minutes. 6 acknak reports that at first, it showed "Read error" in red for the images. The message later changed to "Unable to display" (or something like that). We will continue our testing but hope that this file may prove useful to developers to allow this apparently random image loss problem to be diagnosed further. -- You are receiving this mail because: You are the assignee for the issue.
