Description: Changing default master slide design slow and CPU hogging Steps to Reproduce: 1. Open the attached file 2. Select all the sheets in the Slide Pane (CTRL+A) 3. Menu Slide -> Slide Master Design 4. Select a slide Design 5. Check Exchange background page & Delete unused backgrounds Actual Results: LibO is unresponsive for a while Expected Results: Doesn't seem right to me Reproducible: Always User Profile Reset: No Additional Info: Version: 6.0.0.0.alpha0+ Build ID: 18f80da7a689ab962735c0f657497b8f1ed4d606 CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-07-28_05:15:48 Locale: nl-NL (nl_NL); Calc: CL User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Created attachment 135077 [details] Example file
Created attachment 135708 [details] Callgrind output from master Repro. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: 668ab2e739397e6b095372a1a468bd4f515927b6 CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on August 20th 2017
Created attachment 136803 [details] Bibisect log ~/bibisect-win32-5.1 $ git bisect good c0829f6dfc7c843aa12d06273011e89d89224de2 is the first bad commit commit c0829f6dfc7c843aa12d06273011e89d89224de2 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sun Jul 19 20:25:47 2015 -0700 source f7ed8b99b628625851fb28ec1a3dead710c8871c source f7ed8b99b628625851fb28ec1a3dead710c8871c :040000 040000 647019972266035e876786cbb62b87588a0e78b3 120e5a8a278b1cb047d878eec8ffe8c03cd317cc M instdir -- author Caolán McNamara <caolanm@redhat.com> 2015-06-23 15:54:52 (GMT) committer Caolán McNamara <caolanm@redhat.com> 2015-06-23 15:57:23 (GMT) commit f7ed8b99b628625851fb28ec1a3dead710c8871c (patch) tree 3c1947051b4727e13f8e22f2b518f45e79a5ef60 parent 49002c028da9ca5d7e236ab166104630511b8426 (diff) allow slide design to affect multiple standard pages modify this minimally and select all standard pages selected in the slidesorted, unselect them afterwards and loop over the selected ones. This looks like it could do with a rework to disentangle the master/standard pages stuff, but leave it as is in this commit https://cgit.freedesktop.org/libreoffice/core/commit/?id=f7ed8b99b628625851fb28ec1a3dead710c8871c Note: It was broken before, but in a different way. Not all the sheet where converted before; but it was fast. Now it's slow but working fine
> Note: It was broken before, but in a different way. Not all the sheet where > converted before; but it was fast. Now it's slow but working fine I don't think it's a regression then
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
still rerpo in Version: 6.2.0.0.alpha0+ (x64) Build ID: e7d5bad5ae083da12c3ec4a4a8bdc8b42447a242 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-06_02:55:02 Locale: ru-RU (ru_RU); Calc: threaded but file-example has 105 (!) slides. I don't know how will be work another presentation software (for example PowerPoint) in this case
Dear Telesto, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Telesto, 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