Created attachment 152616 [details] Perf flamegraph 1. Open attachment 112640 [details] 2. Press F5 Stopwatch times for slide to appear: 6.2.4: 2.8 s 6.4: 7.77 s Flamegraph is pointing to alpha blending and unpremultiply operations. Arch Linux 64-bit Version: 6.4.0.0.alpha0+ Build ID: e553b3698f6d8f4f606ebe21ed9857ee09f0c057 CPU threads: 8; OS: Linux 5.1; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 5 July 2019
Repro Version: 6.4.0.0.alpha0+ (x86) Build ID: 849b837d1a3b185a8dd893a8f6eaed53605bcab1 CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-07-05_03:53:49 Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
this are my findings: -oldest 6.2 commit: 6.50 seconds -oldest 6.3 commit: 6.50 seconds -oldest 6.4 commit: 8.50 seconds all with clean profile, so I'm afraid I can't bisect it ...
Also slow with Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL Removing bibisectRequest & regression
Dear Buovjaga, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Tested with 7.4 Linux bibisect repo and it has now gone back to about 2 seconds, so let's close.