Steps to reproduce: 1. Open attachment 147051 [details] from bug 121719 2. Start slide show -> it hangs for 10 seconds before the presentation is displayed Reproduced in Version: 6.2.0.0.beta1+ Build ID: a63cd8bbe7cf881daa8dc7a7f32f3e5ac384e902 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
Regression introduced in range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=aa6c54f337a616c9ca6a39cfc8708657018d8613..bd503faaf61943f25be46bb540023f15606a106a @Caolán, I see some cairo work in the range. Wondering if it's related...
Can not reproduce in Version: 6.0.6.2 Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU threads: 2; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group
confirm with Version: 6.3.0.0.alpha0+ Build ID: 74d6476a045ff2cad36deac51228712d992fb98b CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded
Its probably the RasterOp::Xor in OutputDevice::ClipAndDrawGradientMetafile xor is kryptonite for the cairo rendering
yeah, its that gradient XOR. I can at least parallelize our xor-in-cairo hack with https://gerrit.libreoffice.org/#/c/64111/ which will make it faster, depending on the number of threads available, but maybe alg knows a better way to tease the drawinglayer down a different path that avoids that xor in the first place ?
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/da0afa5ac2b69bcb4b19ec4dd096d7b3f1e50fc9%5E%21 Related: tdf#121721 use premultiply unpremultiply tables It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-6-2": https://git.libreoffice.org/core/+/0aaebad112a2d877450133b737c5b08bf8b2387d%5E%21 Related: tdf#121721 use premultiply unpremultiply tables It will be available in 6.2.0.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
caolanm->xisco: how do you find the timing now ?
it takes 5'45 seconds in Version: 6.3.0.0.alpha0+ Build ID: fcc76610649a9830859f9e2efe2a06dbc6db74da CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded while in Versió: 6.1.3.2 ID de la construcció: 1:6.1.3~rc2-0ubuntu0.16.04.1 Fils de CPU: 4; SO: Linux 4.15; Renderitzador de la IU: per defecte; VCL: gtk3; Configuració local: ca-ES (ca_ES.UTF-8); Calc: group threaded it takes ~10 seconds so it's around 50% faster in master...
FIXED?
probably not, we need to avoid xoring stuff, there was a proposal IIRC in this years tenders to address getting rid of xoring stuff maybe this would fall under that and if it happened make this better
Dear Xisco Faulí, 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
I can't reproduce it in Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 75fe4051320ef9b1f4323fa958e8df3db2066882 CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded Closing as RESOLVED WORKSFORME