Created attachment 133265 [details] bibisect details Working on debian-stretch in the daily Linux dbgutil bibisect repository, I see an increase in the time to process the menu option Insert > "Text Box". In non-dbgutil builds, the times will of course be shorter. It would be interesting to know if they are in proportion. It may be that a non-dbgutil build is fast enough that even the slowed-down response is not worth fixing. For testing, It will be convenient to have (in Linux) `top -d 1 -p $( soffice.bin )` running in a window so that you can see the accumulated CPU time. I am reporting CPU times just because it is easier to watch them than changes in the Writer window. STR --- (1) Open new Writer document. (2) Highlight menu option Insert > "Text Box". (3) Note accumulated CPU time. (4) Take menu option. (5) Wait for accumulated CPU time to stabilize and note the value. (6) Calculate the incremental CPU time from the values noted in steps (3) and (5). Expected : about 1 second Observed : about 12 seconds For comparison, Impress in version 2017-04-28 responds to Insert > "Text Box" in 0.18 CPU seconds. Bibisect points to the 68 commits to master ... commit date s-h -------- ---------- -------- good 8b7f5c9c 2017-04-27 437105b9 bad b8d9ccca 2017-04-28 74ccd02e I am setting keywords perf, regression, bibisected.
I can't reproduce it in Version: 5.5.0.0.alpha0+ Build ID: 6ab249ea6aecef5d3f35d624622a368061cad9c3 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Non-debug master build: At step 3 I had: 0:01.66 At step 5 I had: 0:01.81 5.3.3: Step 3: 0:01.54 Step 5: 0:01.68 So no difference. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: d6c4c576ef71f2294ec8eefc6576a797220e6809 CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on June 18th 2017 Arch Linux 64-bit, KDE Plasma 5 Version: 5.3.3.2 Build ID: 5.3.3-1 CPU Threads: 8; OS Version: Linux 4.10; UI Render: default; VCL: kde4; Layout Engine: new; Locale: fi-FI (fi_FI.UTF-8); Calc: group
Thank you, Xisco and Buovjaga. I am setting status RESOLVED INVALID.