Description: When I add a bigger picture to my document, scrolling across it slows writer down and causes stuttering. Takes a few seconds at the beginning (maybe the image gets loaded?), and then scrolling continues, but a little bit slower than standard. It was a PNG graphic in my case. Steps to Reproduce: 1. Place a big picture in a document 2. Get it out of sight 3. Scroll back to the picture Actual Results: Stuttering and slowdown Expected Results: Smooth scrolling Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Please attach a document. I'm hesitant to mark this as NEW just because we are well aware that our image handling isn't fantastic. There are dozens of reports that are probably duplicates of this (or have a similar root problem). To say the least, we need a document. Marking as NEEDINFO, once you attach, mark as UNCONFIRMED. Thanks Minor: Can slow down but will not prevent high quality work; Low: Default for bugs that do not prevent high quality work.
Created attachment 127915 [details] Big picture
Created attachment 127916 [details] Document with big picture
Here is my example. Scrolling in this case doesn't stutter as heavy as in my real case - maybe it's due to the document not containing as much data, maybe it's due to the image, not containing a real schematic. But I can recognize the effect.
Version: 5.3.0.0.alpha0+ Build ID: 28d3a6af0703c666d80e38c9c4b86024d830994d CPU Threads: 2; OS Version: Linux 3.16; UI Render: default; Locale: en-US (en_US.UTF-8); Calc: group Confirmed. Like I said, almost definitely a duplicate of an already existing bug but I'll push to NEW. If you can search through the current bug list and see if you can find a duplicate of this one that would be fantastic. Also please come say hi to the QA team at http://webchat.freenode.net/?channels=libreoffice-qa We're always looking for new cool people to come and assist :)
Dup of bug 87485 ?
Looks like it to me. *** This bug has been marked as a duplicate of bug 87485 ***