When working with hi-res images the system is extremely slow. It is as if the system works on the full uncompress image in full resolution instead of a scaled down version of the same.
Steps to Reproduce:
1. New text document
2. Insert attached image
3. Write text
The program is now very slow.
Same speed as if the image had been in low-res.
Looking at the memory and CPU usage it looks as if Writer is working on the full-resolution image all the time.
It would be much preferable if Writer cached a version scaled for the current need and worked on that; and only recomputed a new scaled version when the image is resized or zoom is changed.
Microsoft Word has no problem using the hi-res image.
User Profile Reset: No
(Thanks for fixing the bug in 188.8.131.52, that made it impossible to work with hi-res images at all).
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36
Created attachment 136896 [details]
Very high resolution PNG
I confirm, that LO gets really slow. It requires about 850MB RAM.
Version: 184.108.40.206.alpha0+ (x64)
Build ID: 465092047d5fa6ec6dd369372e712d76554570ff
CPU threads: 4; OS: Windows 6.19; UI render: GL;
TinderBox: Win-x86_64@42, Branch:master, Time: 2017-09-26_23:16:01
Locale: de-DE (de_DE); Calc: group
No repro with
Versie 220.127.116.11 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89)
No repro with:
Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28
Created attachment 137560 [details]
I bisected it on Linux to following commit based on the memory usage
Author: Armin Le Grand <email@example.com>
AuthorDate: Thu Oct 31 14:43:21 2013 +0000
Commit: Caolán McNamara <firstname.lastname@example.org>
CommitDate: Tue Nov 5 15:24:18 2013 +0000
Resolves: #i123500# unified Graphic processing to use GraphicPrimitive2D
(cherry picked from commit f5d69b2b8b002ca6905496a9d9065ef76b5641d7)
Adding CC to Armin Le Grand
*** This bug has been marked as a duplicate of bug 80659 ***
Bug 80659 doesn't seem appropriate
*** Bug 104296 has been marked as a duplicate of this bug. ***
Problem is still in present in:
Version: 18.104.22.168 (x64)
Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb
CPU tråde: 4; Styresystem: Windows 10.0; Gengiver af brugergrænseflade: Standard;
Lokalisering: da-DK (da_DK); Calc: CL