Description: Moving a sheet with a chart based on a datarange to a different tab position takes 30 seconds until moved an still unusable for 40 seconds afterwards Steps to Reproduce: 1. Open the attached file 2. Move sheet 2 before 500k formula sheet Actual Results: 30 seconds before sheet moved.. Click the sheet it hangs again Expected Results: 10 seconds and usable after move Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 7.0.0.0.beta1+ Build ID: c344de1b9985b6ca10b354e24151d0bdf92dc20e CPU threads: 2; OS: Linux 5.3; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded but not in 4.2
Created attachment 161782 [details] Bibisect log Bisected to 3abe790c27b619aa5e9848f34b152069527473bf is the first bad commit commit 3abe790c27b619aa5e9848f34b152069527473bf Author: Matthew Francis <mjay.francis@gmail.com> Date: Thu May 28 21:13:02 2015 +0800 source-hash-0ce6d9bcea7c37a7cb2c42e8393e2e20780bd171 commit 0ce6d9bcea7c37a7cb2c42e8393e2e20780bd171 Author: Markus Mohrhard <markus.mohrhard@collabora.co.uk> AuthorDate: Thu Apr 17 02:02:15 2014 +0200 Commit: Markus Mohrhard <markus.mohrhard@googlemail.com> CommitDate: Thu Apr 17 02:08:59 2014 +0200 limit the range shrinking in charts to really large ranges, fdo#70609, Also improves the situation for fdo#55697. It is just the fist step to a better algorithm. Change-Id: I15de1ca6604e585fcf5690f0d903c757d641e765
Created attachment 161783 [details] Example file
about 15/15 sec. here, set to new as improvements would be nice, but not a 'big issue' Version: 7.0.0.0.alpha1 Build ID: 6a03b2a54143a9bc0c6d4c7f1... CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: de-DE (en_US.UTF-8); UI: en-US Calc: threaded
The same commit causes a delay in removing the sheet (18 seconds vs 32 seconds). And quite a bump in memory usage while deleting. 420 MB versus 1100 MB peak
Another version 1. Cut the Chart on sheet 2 2. Wait 60 seconds.. prior 20 seconds Notice also the file opening time -> Slower Memory usage showing grah 745 MB after the commit 227 MB before the commit
Adding CC: to Markus Mohrhard
Bug 70609 comment 2 So the shrinking of data ranges is hurting us here. I was never a big fan of this feature but it seems that we finally need a proper solution for the problem. The problem is that the content is not yet imported and we are already importing the chart so shrinking to the used data range is wrong. I'll limit the feature for now to cases where it won't hurt us too much and will think about proper solutions.
Still happens Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 172e208e6b0674f42c301c5ee5e280e9138ba1b4 CPU threads: 2; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded Jumbo