Description: Crash Steps to Reproduce: 1.Open attachment 159163 [details] 2. Select all sheet 3. Sidebar -> Master slides 4. Start applying.. after 5 or so.. crash Actual Results: Crash Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.beta1+ Build ID: 2891e91a513520d68ea2b8c59c14335861a15253 CPU threads: 2; OS: Linux 5.3; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
This bug is no longer reproducible in versions: 6.4.4.2 (Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff) 7.1.0.0.alpha0 (Build ID: 4c4b3218b8595a9809ffade0cfd064f3d9335dff ) After switching between styles for some time, application slowed down for a moment but no crash occurred.
I only reproduce a gradual, but quite noticeable slowdown in responding to the changes, when I use the gen backend. This is already observed in the oldest commit of Linux 6.3 repo. With Linux 50max repo, I observe a hang/crash. However, the oldest commit of 50max / latest of 44max do not show any available master templates in the sidebar. I don't know of another way to apply them. Would be interesting, if you got a backtrace of the crash with Linux-rpm_deb-x86_64@86-TDF-dbg You can force the gen backend (and start gdb backtrace session) from the terminal by launching with SAL_USE_VCLPLUGIN=gen /path/to/soffice --backtrace Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: 52d70047c694d4e0c8bbf843c895d86492735f3f CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: x11 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 25 June 2020
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