Description: Interacting with hi-resolution image in view becomes slow. Memory drops as if image get swapped to disk Steps to Reproduce: 1. Open a process monitor (to monitor ram usage) 2. Open the attached file 3. Memory usage jumps to 1,1 GB on file open (OK; older versions 715 MB or so) 4. Wait couple of seconds: memory usage drops to 600 MB (older have more of a delay up 20 seconds) 5. Select the image and start dragging it (lag). At same time memory goes back to 1,0GB and drops again after releasing the image Actual Results: Memory gets freed, but at quite some performance penalty Expected Results: Image on the 'active' page being kept in memory for smooth interaction Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 220ef19df9de6ee7a99173a514402a9e701748d1 CPU threads: 4; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: CL threaded and in Version: 7.0.7.0.0+ (x64) Build ID: 626ea4e62a3e5005fe9825923a1c0c5bdb61cc08 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL also in Versie: 6.3.0.4 (x86) Build ID: 057fc023c990d676a43019934386b85b21a9ee99 CPU-threads: 4; Besturingssysteem: Windows 10.0; UI-render: standaard; VCL: win; Locale: nl-NL (nl_NL); UI-taal: nl-NL Calc: CL also in Version: 6.1.6.3 Build ID: 5896ab1714085361c45cf540f76f60673dd96a72 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: nl-NL (nl_NL); Calc: CL fine with Versie: 6.0.4.1 Build ID: a63363f6506b8bdc5222481ce79ef33b2d13c741 CPU-threads: 4; Besturingssysteem: Windows 10.0; UI-render: standaard; Locale: nl-NL (nl_NL); Calc: CL
Created attachment 201263 [details] Sample (compressed with 7zip)
The difference in memory usage of 1,1 today and 700 MB for versions below LibreOffice 7.0.0.3 likely due Skia caching + bug 142789
Apparent dimensions: 6.52" x 11.51" at 1522 DPI 30548 KiB Image size: 74.05" x 104.67" (9924 x 14027 px)
Cause: the default GraphicMemoryLimit (expert setting). increasing it from 300 MB to say 1000 MB and the issue vanishes