Description: Inserting a new sheet very slow Steps to Reproduce: 1. Open attachment 142401 [details] from bug 117896 2. Right-click sheet KROSCEK - Insert a sheet before -> Wait Actual Results: Takes very long (minutes) Expected Results: More or less in a blink Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 191288d6a7fb52b31038a21c4e71ee57ffa3bacd CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL and in 4.0.0.3 Sheet is no working properly in 3.5.7.2 and 3.3.0
Flamegraph would be nice, if reproducible of course
First let's wait for some feedback about other Flamegraphs.
Another way to reach the same goal 1. Open the attached file 2. Drag Master Absensi before Master GW 3. Click KROSCEK -> Hang
Another way the reproduce 1. Open the file 2. Save the file -> Set row height manually first.. to 0,50.. loading will take quite some time without.. bug 124098 3. Open the file 4. Click Master sheet
confirm this issue. took me 164s only to insert an empty sheet after KROSCEK. Version: 6.4.3.2 (x64) Build ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Confirm with Version: 7.0.0.0.beta1+ Build ID: c344de1b9985b6ca10b354e24151d0bdf92dc20e CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
Created attachment 174955 [details] Perf flamegraph (In reply to Telesto from comment #0) > Steps to Reproduce: > 1. Open attachment 142401 [details] from bug 117896 > 2. Right-click sheet KROSCEK - Insert a sheet before -> Wait Traced for quite some time, but did not wait until the very end. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: e6a8d312d3d7e5d81c56d5ccc0508116dd283f1f CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded
*** This bug has been marked as a duplicate of bug 139444 ***