There has been an image-handling renovation. You might want to test with a fresh master build to see, if the situation is changed: https://dev-builds.libreoffice.org/daily/master/Win-x86_64@42/current/

nah no thanks...i'm just normal user,beta is a no go for me.its not like this ticket getting close over time...

(In reply to fake name from comment #2)
> nah no thanks...i'm just normal user,beta is a no go for me.its not like
> this ticket getting close over time...

The master build installs separately to your stable install.

still have to pass on that...i dont want to take risk using alpha/beta/nightly software whatsoever...i use stable version only, which is why i'm using still lo

(In reply to fake name from comment #4)
> still have to pass on that...i dont want to take risk using
> alpha/beta/nightly software whatsoever...i use stable version only, which is
> why i'm using still lo

As Buovjaga already said, the master build is installed *separately*, your stable version is still there and untouched. You can delete the master build if you do not need it any longer. Use the master for testing whether the error still occurs there, and the stable version for your normal work. So there's no risk. And if the error is really gone, you can always use this master in case you have the same problem gain with the same or another document, until you have updated your stable system to a version where the error does no more occur.
By the way, the link Buovjaga provided is, I think, for 64-bit LibO, which might not work for your system, but I am not sure of that.
Anyway, there is an easy way to install a newer version of LibO in parallel to your stable system, for Windows: look at
https://wiki.documentfoundation.org/SI-GUI.

That said, I have not so much hope that the new version will solve your problem. I have many Writer documents with dozens of images and never encountered such a problem. In adddition, your description is very vague, I would not know how to try to reproduce the problem other than what I did with my documents, and I cannot reproduce it.
With such sparse information I fear nobody will look closer to the problem. Does it arrive for a single document or could you reproduce it with another, new document? Did you reproduce it with the same set of images or also with others? What does "put a lot of image in that" mean? Many images, a large image, then which? I you didn't save, you should recognize which is the last image loaded (if you mena many images) correctly into the file; did you test only with the image that could not be loaded?
Etc. These questions should be handled before anyone will know what you mean.

> That said, I have not so much hope that the new version will solve your
> problem. I have many Writer documents with dozens of images and never
> encountered such a problem. In adddition, your description is very vague, I
> would not know how to try to reproduce the problem other than what I did
> with my documents, and I cannot reproduce it.
> With such sparse information I fear nobody will look closer to the problem.
> Does it arrive for a single document or could you reproduce it with another,
> new document? Did you reproduce it with the same set of images or also with
> others? What does "put a lot of image in that" mean? Many images, a large
> image, then which? I you didn't save, you should recognize which is the last
> image loaded (if you mena many images) correctly into the file; did you test
> only with the image that could not be loaded?
> Etc. These questions should be handled before anyone will know what you mean.

did your setting same as mine?look at additional info...most of my image is screenshot from firefox screenshot, how many page your document have?mine is at 40-50 in a file that i open frequently,there a 10-15 table too, and like the report say the bug happen sometimes, and i say it only reproduceable when the image itself say "read error"...i dont know how to say anymore, it happen to me T_T.well if it doesnt happen to anyone else, then i'm dont know what to say anymore...

yes.same set of image, i recognize because i put title before image, for a few image the size is 1170 x 605, the image itself disappear from document not could not be load (doc>7zip open archive>image folder>no image) and the document have password to open it...currently trying with new document using windows library public picture, some empty table, literally this whole bug report copy paste into the document (unformated text) until it reach 50 pages...

ok...i try it with new document(no password), i'm sure 100% now it reproduceable,
16 image, 7 table, unlimited copy pasted of this report(unformated text) until the document reach 100 page, document is .odt 10mb sized, after "read error" & save,the document size just a few kb and 7zip>open archive>no folder for image/picture.i think this was cause by remove from memory after hour:min, because if i change it to 00:00 the file was fine even after 2 hour(i only try once, could  be  lucky)...hope that help somehow

(In reply to fake name from comment #8)
> ok...i try it with new document(no password), i'm sure 100% now it
> reproduceable,
> 16 image, 7 table, unlimited copy pasted of this report(unformated text)
> until the document reach 100 page, document is .odt 10mb sized, after "read
> error" & save,the document size just a few kb and 7zip>open archive>no
> folder for image/picture.i think this was cause by remove from memory after
> hour:min, because if i change it to 00:00 the file was fine even after 2
> hour(i only try once, could  be  lucky)...hope that help somehow

If you can attach the file, it can help.

I must say that I still do not understand what happens.

But first here are my settings at the right, which I'm sure are the default settings; at left are yours.

memory setting:
use for lo=390mb              190
per object=90mb                12
remove from memory=10m         10
cache for inserted object=90   20 
autorecovery disabled          enabled
view>graphic output=all tick except blacklist & below blacklist it say GL is currently disabled            same with me

I wonder why you changed the second setting to such a high value, since your file has only 10 MB and this is for a single object. But I have no idea if that could be the reason for your problem.
The page for these options has been removed in 6.0, by the way. Therefore I recognized that you must be using version 5.4 or earlier. Why not change to 6.0, which is available since the end of January and is running fine.

As size is concerned: Most of the files I mentioned are much larger than 10 MB, the largest has neqrly 40 MB and contains 77 images.

But back to what is happening!
When does that mysterious §read error" appear? After you inserted an image, after another action, or - as your text suggests - after some time without your doing?
Has the document with all the images been saved already - manually - by you? Do you mean that you can open this again and it's OK by "... it's still there"?

(In reply to Gerhard Weydt from comment #10)
> I must say that I still do not understand what happens.
> 
> But first here are my settings at the right, which I'm sure are the default
> settings; at left are yours.
> 
> memory setting:
> use for lo=390mb              190
> per object=90mb                12
> remove from memory=10m         10
> cache for inserted object=90   20 
> autorecovery disabled          enabled
> view>graphic output=all tick except blacklist & below blacklist it say GL is
> currently disabled            same with me
> 
> I wonder why you changed the second setting to such a high value, since your
> file has only 10 MB and this is for a single object. But I have no idea if
> that could be the reason for your problem.
> The page for these options has been removed in 6.0, by the way. Therefore I
> recognized that you must be using version 5.4 or earlier. Why not change to
> 6.0, which is available since the end of January and is running fine.
> 
> As size is concerned: Most of the files I mentioned are much larger than 10
> MB, the largest has neqrly 40 MB and contains 77 images.
> 
> But back to what is happening!
> When does that mysterious §read error" appear? After you inserted an image,
> after another action, or - as your text suggests - after some time without
> your doing?
> Has the document with all the images been saved already - manually - by you?
> Do you mean that you can open this again and it's OK by "... it's still
> there"?

the reason why the setting are like that mainly because of ocd.9 is my number.let just say you already have a document prepared for testing(or just copy that 77 image document), open it then scroll to a page that have no picture(let just say 5 page are used for text in the middle of document), leave it for 11-13 minutes for remove from memory to kick in(you can browse internet or whatever it is), now scroll through the whole document to check if the image show "read error", because i tested & it happen,i think this also happen in lo6 because before using lo5 i try lo6 from portableapps first(6.0.0 i think,at that time i though it was because fresh=beta(bug?)),no setting change though except notebookbar...

I'm sorry to say that I cn't reproduce the bug. I tested it in 6.0.2.1 with my settings as in comment 10, then in 5.4.6.1 with exactly your settings.
I opened a document I had prepared with 777 images, 18 tables, 77 frames and some other text, it contains 113 pages and is about 40 MB. I scrolled to a page without an image and left it rather for some hours than only for more than 10 minutes. Afterwards I scrolled through the entire document, from the first to the last page, but got no message "read error".
Is there still a difference to what you have been doing?

The cause for your problem may perhaps lie somewhere in your system outside of LibreOffice, or in conjunction with LibreOffice.
You say you are using Windows NT 6.1. According to Wikipedia this is Windows 7, but I am no specialist, and following other remarks in this article this could well be an internal name which is supplied in some circumstances.
Now I use Windows 10, but before I used Windows 7, and at that time I already often worked with such files with dozens of images, too, and I never had the problem.

I fear I cannot help you, but if you have a different scenario for testing, I can do some more testing.

Created attachment 141747 [details]
This is file i used to test the bug

after 6 time trying "read error" appear & this file is the unsaved version of it...

Created attachment 141748 [details]
this is the result after save

this file is saved version after "read error" appear,i use save as.

try libreoffice 5.4.5 from portableapps (easy to delete later)

my setting:
user data>untick use data for document properties
memory>same as describe in this report
view>same as describe in this report
advance>enable experiment(for notebookbar),untick java
load/save general>untick autorecovery

i already attach the file "test before.odt & test after.odt",it took me 6 tries before "read error" appear,try open test before.odt and scroll to last page then write a few alphabet/word and save wait 11-13 minute for remove from memory to kick in, if "read error" does not appear close libreoffice(not document) then open it again & try again.
if the bug still not reproduceable then i dont know what to say anymore...i mean if you type on google "image disappear in libreoffice writer" some of the result actually say something about "read error" but that just about it, no detail on how to fix it whatsoever...if this still not helping then i guess im stuck.

I am sorry that I still cannot reproduce the error.
I installed version 5.4.5.1 and set all the options as you indicated in comment 15. I followed your instructions how to open and edit the document, letting it rest for more than ten minutes before doing again anything with it, and I did this 9 times, nothing happened to the file, all images were there.

But I also looked for these issues in the internet and especially in Bugzilla, and there is a lot of recent discussion about this or related subjects, so I believe that, in spite of my not reproducing the error, your case is of general importance. But it seems to be a hard nut to crack.

Your file would be very helpful, because you can reproduce (often enough) the error with a standard procedure, as you described in comment 15, so hopefully someone else can reproduce that, perhaps with an older Windows version than Windows 10, which I use.

Yes, there is bug 98686 for images disappearing from Impress. The bitmap handling renovation happening currently in 6.1 is hoped to remedy the situation. That is why I asked the reporter to test with it. I understand it is not fun to test such a scenario requiring hours of time.

ok i just notice this today...ram usage after opening my document(not the uploaded one) is around 120mb++ but when "read error" appear it only use less than 60mb...the process is soffice.bin...is this normal?

rather than os specific problem can this problem caused by software like ccleaner?i mean ccleaner clean temp file after all (untick only delete temp file older than 24 hour)...can you try testing again in win 10, same procedure but use ccleaner after opening document this time?

im not too sure about this though since my friend msoffice 2007 word doc doesnt seem to be affected even if the temp file it created got deleted, but i noticed libreoffice temp file which i think is the image since i open my doc in lo(no tmp file created yet but just folder) and then i hover to image inside document(numerous tmp file created inside the folder).

btw the image doesnt dissapear yet after i run ccleaner so i think:

open doc(chk all image)(image tmp file created)>run ccleaner(delete tmp file that wasnt in use)>lo memory clean kick in(thus it check tmp file for image, image not found thus read error)>saving cause image dissapear...

and please dont ask why my ccleaner setting like that, different ppl diferent use

I cannot find that CCleaner does anything which could be connected to your error.
I opened my document with many images (38 MB) and then ran CCleaner. The settings for CCleaner include deletion of temorary files, and deletion of files not older than 24 hours is not excluded (the option you name is unticked, that will be standard then). I encountered no error message when saving the file, the file size remains unchanged.
I then looked for temporary files in the system, and found a directory ...users...AppData\Local\Temp\xxx.tmp. It had a size of 735 KB when I first looked at it. Then I opened my large documentwith images again: it's size changed to 58.7 MB. I had not done anything else in the meantime, so I must assume that the additional files in this directory were created by opening the document. When I close it, the size is reduced to 735 KB, again. This is reproducible. The number of files in this directory switches between 29 and 69, depending on whether my document is open or not.
And when I ran CCleaner while my document was open, the size of this directory did not change! I infer from that that CCleaner does not affect the temporary files created by opening the LibO document. Moreover, the directoy contains files created some hours before I ran CCleaner (twice), and they are still there. They will certainly be deleted some time, but obviously not by CCleaner (or at least not immediately), but rather by another mechanism.
So I think that CCleaner has nothing to do with your problem.

wew...that so different than mine...my temp file got deleted almost immediately when running ccleaner(leaving only 1 tmp file) and closing lo(deleting whole tmp folder)...i'm seriously think the cause was because of tmp file deletion...can you try again but now like this :

make sure first few & last page are only text before testing(to make sure the tmp file created are actually image and not other thing), make sure there no lo temp folder yet in appdata\local\temp.

open lo(empty temp folder will be created do not close your windows/file explorer yet),first few page is text, now press navigator type & go to your last page that also only text,check lo temp folder(still empty or not*mine still empty btw).

now scroll through your document 1 by 1 for image to load(check temp folder, there should be same amount of tmp file as your image amount),now go to first or last page for testing,delete all temp file not the folder,wait for 11-13(just to be sure) minute for memory clean to kick in,scroll through your doc again to check all those image...

let see if those read error frame appear or not

btw after read error appear it seem that tmp file are recreated again once you scroll through the doc.

Would you mind to try UN-check Use OpenGL for all rendering and restart Libre if the problem is gone?

https://bugs.documentfoundation.org/show_bug.cgi?id=118289

I use Libre for similar purpose for composing notes with lots of screen shots and pictures, and I found this issue years ago and had to turn to other ways of doing so. With new releases 5.x 6.x I found the same issue and late of last week found it's because of OpenGL for all rending (at least for my very old PC with KDE NEON)...

Dropping this as a reference: https://blog.documentfoundation.org/blog/2018/06/19/image-handling-rework-for-libreoffice-collaboras-tender-results/
Setting to needinfo as this is probably fixed in 6.1, so if the reporter does not want to try a separate install, the have to wait for the stable.

(In reply to baifcc from comment #23)
> Would you mind to try UN-check Use OpenGL for all rendering and restart
> Libre if the problem is gone?

already tried just now...still happened.i 100% think its because of those temp file like i describe above, by any chance do you use bleachbit or anything equivalent of it?

(In reply to Buovjaga from comment #25)
> Dropping this as a reference:
> https://blog.documentfoundation.org/blog/2018/06/19/image-handling-rework-
> for-libreoffice-collaboras-tender-results/
> Setting to needinfo as this is probably fixed in 6.1, so if the reporter
> does not want to try a separate install, the have to wait for the stable.

will wait for stable...tq for informing

(In reply to fake name from comment #26)
> (In reply to baifcc from comment #23)
> > Would you mind to try UN-check Use OpenGL for all rendering and restart
> > Libre if the problem is gone?
> 
> already tried just now...still happened.i 100% think its because of those
> temp file like i describe above, by any chance do you use bleachbit or
> anything equivalent of it?
> 
> (In reply to Buovjaga from comment #25)
> > Dropping this as a reference:
> > https://blog.documentfoundation.org/blog/2018/06/19/image-handling-rework-
> > for-libreoffice-collaboras-tender-results/
> > Setting to needinfo as this is probably fixed in 6.1, so if the reporter
> > does not want to try a separate install, the have to wait for the stable.
> 
> will wait for stable...tq for informing

Thank you

ok...i just try lo 6.1 portable...it seem the problem is gone for now(didnt test for a long time, just 30-40 minutes), but should i make a new bug report for :

1. new notebookbar ui, the new one look neat and clean but some button like rtl/ltr is gone.i know its still experimental and not final but should i make bug report for it?i kinda like the old 5.4 design.

2. i notice lo 6.1 create a 1 gibberish.tmp(only happen when saving doc) file in the same location as doc & lock file.the old one feel like save>overwrite but the new one feel like save>create new file>delete old file.is there a way to setting back to the old one?because i hide some of my doc(hidden attributes) but after i save using lo 6.1 the file is not hidden anymore.help?

(In reply to fake name from comment #28)
> ok...i just try lo 6.1 portable...it seem the problem is gone for now(didnt
> test for a long time, just 30-40 minutes), but should i make a new bug
> report for :
> 
> 1. new notebookbar ui, the new one look neat and clean but some button like
> rtl/ltr is gone.i know its still experimental and not final but should i
> make bug report for it?i kinda like the old 5.4 design.
> 
> 2. i notice lo 6.1 create a 1 gibberish.tmp(only happen when saving doc)
> file in the same location as doc & lock file.the old one feel like
> save>overwrite but the new one feel like save>create new file>delete old
> file.is there a way to setting back to the old one?because i hide some of my
> doc(hidden attributes) but after i save using lo 6.1 the file is not hidden
> anymore.help?

1. As the NB is still in flux, you should always follow the latest master: https://dev-builds.libreoffice.org/daily/master/Win-x86_64@42/current/
and check the open reports https://bugs.documentfoundation.org/showdependencytree.cgi?id=102062&hide_resolved=1

In this case, it seems to be a conscious decision. For example, in the Tabbed bar, you can reach the text direction in the Home tab by clicking on the "Home" dropdown in the top right.
Bug 101513 is about customising the NB. So I don't think you should open a new report for it.

2. I think if you opened a report for that thing, it would just be closed as notabug.