Description: When I open the attached pdf in draw, it spins infinitely. Opening other pdfs seems to be OK, though. Steps to Reproduce: 1. open the pdf Actual Results: draw is spinning on CPU Expected Results: pdf is opened. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Created attachment 134723 [details] pdf to reproduce
Created attachment 134724 [details] thread apply all bt in gdb when this happens I do not have debug symbols installed because there are none available on opensuse AFAICS.
Created attachment 134725 [details] thread apply all bt in gdb when this happens with debuginfo installed In the end, I updated to 5.4.0.2 from LibreOffice:Factory project: https://build.opensuse.org/package/show/LibreOffice:Factory/libreoffice and there is also debuginfo. So the backtrace shows, that we are spinning in pdfi::PageElement::resolveUnderlines.
Confirmed in - Version: 6.0.0.0.alpha0+ Build ID: ddadcb4f4a2bc6538c219a0a577bdf5999015150 CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group - Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e - LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
** 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 happens with 6.1.0.1.
Dear Jiri Slaby, 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 happens with 6.2.5.2.
On my four year old notebook, at T450 with Intel Core i7-5600U CPU @ 2.60GHz LibreOffice 7.0 alpha manages to open this after 5 minutes. An strace shows a long list of calls to sbrk(). Is this an improvement, or did you not wait that long (or used a significantly slower machine)?
(In reply to Gerald Pfeifer from comment #9) > Is this an improvement, or did you not wait that long (or used a > significantly > slower machine)? Oh really -- it takes ~ 5 mins, I never waited for that long. libreoffice-6.4.1.1-1.1.x86_64
Created attachment 158444 [details] perf report of draw According to these perf measurements, Draw seems to spend significant time in pdfi::PageElement::resolveUnderlines which contains this FIXME: // FIXME: currently the algorithm used is quadratic // this could be solved by some sorting beforehand That function searches the document for horizontal lines and removes them if they underline some text (and makes the text underlined instead). Well, the document contains many horizontal lines. The algorithm should be optimized or should time out after a while (not 5 minutes).
Dear Jiri Slaby, 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
Still slooow with (mostly) current -dev builds: Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 2b924f0d83ce63882e7d14a2b51cc645c2532920 CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5cd9de202765e243e41416802f3e4486b8a96f16 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: CL threaded opens the PDF instantly closed as WFM
Still slow in 6.4.8.0.0, 7.2.8.0.0, and Version: 7.4.8.0.0+ / LibreOffice Community Build ID: 603f915294a10f11b4199dfd28704a77f4e05abd CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US with with ~113s for the latter on my i5-10210U CPU @ 1.60GHz system (which is three years old, cf. comment #9 for older measurements on an older system). Version: 7.5.2.0.0+ (X86_64) / LibreOffice Community Build ID: bad4f41a69fe3fb08191b839f0c9389683685855 CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US and Version: 7.5.4.0.0+ (X86_64) / LibreOffice Community Build ID: f794d79a334413dd1e5c4f4997d11047170024ef CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US are indeed down to about 5, 6 seconds, as is current head Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2e57755f72907e4bb604a8ba32edbd6c253ee57c CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US In other words, this likely was addressed in earlier 7.5 development.