Created attachment 160669 [details] Original bug document Moving to slide 9 makes LibreOffice run busy for ~60 seconds while consuming 100% CPU after showing the slide. It is *not* the transition to the next slide that causes that, it is "arriving" at slide 9 even though it's rendered already. How to reproduce: 1. Open deck 2. Go to presentation mode 3. Proceed slide by slide with <space> or <right-arrow> 4. Notice how this stops between slides 9 and 10 (and again Tested with Version: 7.0.0.0.alpha1+ Build ID: 6ba74150866d71469827de9f4f19268dfa7db137 CPU threads: 4; OS: Linux 5.6; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-05-07_15:09:13 Calc: threaded Originally reported against openSUSE at https://bugzilla.suse.com/show_bug.cgi?id=1171015at
Oh, and all Intel hardware (so none of the typical NVIDIA and friends issues).
Confirm on all versions. Including 7.0, but also on Version 3.6.7.2 (Build ID: e183d5b
Created attachment 181337 [details] Minimized example file from PP 2016 Looks like there is a bitmap filled shape in the slide layout, which is rendered very slowly in slideshow mode. Still bad in: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: a4ab155ae15e9e6d4deb157634f8b86c87fcbde4 CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded This never seemed to be good, not a regression.
Dear Gerald Pfeifer, 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
This still appears with yesterday's nightly snapshot of head using the Minimized example. Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d5d4e1334957abc29c5c4f543a8cd15a5aaf8748 CPU threads: 12; OS: Linux 6.9; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US
Comment on attachment 160669 [details] Original bug document Let's focus on the minimized example; obsoleting the original bug document.