Created attachment 123466 [details]
A test-file for this bug; I often use this file
Insert a few images in one document and some longer text, so you have a dozen pages to scroll up and down. It freezes or stops for seconds sometimes. I have a large document you can test with (600 pages). I think it should only create the image resource when scrolling to a specific page that has images and release it as soon as the scrolled view has no image. I have a quite performant laptop and I get this (quad core intel i7, 12GB RAM), I do not think is should act like this. Please test with the smaller file I attached.
This is most definitely a duplicate - someone just needs to find it.
I only get a slight lag, when the images are loaded *from the web*. I do have a beefy new desktop.
Joel is right, though, in that there are a bunch of "slow scrolling with images" like bug 80659 and the "see also" entries in it.
Btw. maybe you would like this: bug 51609
64-bit, KDE Plasma 5
Build ID: 18.104.22.168 Arch Linux build-1
CPU Threads: 8; OS Version: Linux 4.4; UI Render: default;
Locale: fi-FI (fi_FI.UTF-8)
You are right Buovjaga, it looks like bug 51609, but considering it was first reported in 2012 and 4 years later pasted content from web still appears by default as a link (text is ok, but for images it is not, using it without internet makes the file inoperable) should get attention again.
PS: I discovered I can go to Edit - links and Break links. Images seem to show in the file. I hope I don't break my files.
You seem to dig bug 51609, so I'm closing this as dupe :)
*** This bug has been marked as a duplicate of bug 51609 ***
(In reply to florin.arjocu from comment #3)
> You are right Buovjaga, it looks like bug 51609, but considering it was
> first reported in 2012 and 4 years later pasted content from web still
> appears by default as a link (text is ok, but for images it is not, using it
> without internet makes the file inoperable) should get attention again.
Just a heads up here that I've talked to several experienced developers over the years about this and the truth is it's a nightmare to fix. For a volunteer to take this on would take tens or even hundreds of hours, they would have to be really skilled, and incredibly patient. Ideally....some enterprise user at some point will pay a certified developer (company or individual) to fix it properly, else, it's my guess that this isn't going anywhere fast.