Description: Resizing of an image is slow depending of the chosen template Steps to Reproduce: 1. Open the attached file 2. Enlarge the image by selecting it an dragging a corner -> quite choppy Actual Results: Resizing is quite choppy Expected Results: Resizing should be smooth as it was before Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 5.5.0.0.alpha0+ Build ID: d57e6cd9dcc96112994ca2b14ac45896e86b26e5 CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-05-18_22:43:07 Locale: nl-NL (nl_NL); Calc: CL and in Versie: 4.4.6.3 Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d Locale: nl_NL but not in Version: 4.3.0.4 Build ID: 62ad5818884a2fc2e5780dd45466868d41009ec0 User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Created attachment 133431 [details] Example file
It's choppy on Win, but not on Lin. Maybe I should do a callgrind on Lin anyway. I confirmed it was not choppy before. Version: 5.5.0.0.alpha0+ Build ID: b08217989558addbcaded122a4e7211ae24bbcff CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-05-31_06:31:36 Locale: fi-FI (fi_FI); Calc: group Arch Linux 64-bit, KDE Plasma 5 Version: 5.5.0.0.alpha0+ Build ID: c855400e9686ddd8bcba5691393f839f6f52c966 CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on June 2nd 2017
Created attachment 133822 [details] Callgrind output from 5.5 Arch Linux 64-bit, KDE Plasma 5 Version: 5.5.0.0.alpha0+ Build ID: c855400e9686ddd8bcba5691393f839f6f52c966 CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on June 2nd 2017
Telesto: I was going to try and bibisect this, but I noticed that the default resizing method changed from 4.3 to 4.4. In 4.3, the resizing is not proportional by default. In 4.3 you have to press down the Shift key while you resize to get the same method as in 4.4 and newer. With this in 4.3, it is also a bit choppy. Can you re-test with Shift-drag in 4.3 and try to compare and give your opinion? I still think it is a bit slower in 6.1. In 4.3 it also crashes after Shift-dragging for a bit.
*** Bug 117727 has been marked as a duplicate of this bug. ***
(In reply to Buovjaga from comment #4) > Telesto: I was going to try and bibisect this, but I noticed that the > default resizing method changed from 4.3 to 4.4. In 4.3, the resizing is not > proportional by default. In 4.3 you have to press down the Shift key while > you resize to get the same method as in 4.4 and newer. With this in 4.3, it > is also a bit choppy. > > Can you re-test with Shift-drag in 4.3 and try to compare and give your > opinion? I still think it is a bit slower in 6.1. In 4.3 it also crashes > after Shift-dragging for a bit. A different approach, probably the same issue (bug 117727) --> Dragging a fontwork over the sunset template is rather slow Steps to Reproduce: 1. Open Impress 2. Apply the sunset slide template (similar for focus template) 3. Insert a fontwork 4. Drag it around & monitor CPU
(In reply to Telesto from comment #6) > A different approach, probably the same issue (bug 117727) > > --> Dragging a fontwork over the sunset template is rather slow > > Steps to Reproduce: > 1. Open Impress > 2. Apply the sunset slide template (similar for focus template) > 3. Insert a fontwork > 4. Drag it around & monitor CPU Same CPU use with 4.3 and 6.1
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