Created attachment 73233 [details] Example file with hign CPU use while scrolling LibO Version 4.0.0.1 (Build ID: 527dba6f6e0cfbbc71bd6e7b88a52699bb48799) on Windows XP SP3 Russian RTF is opened, but if we try to scroll down document to the second page, everything freezes. While scrolling CPU use jumps from 50% to 100% on Pentium Dual-Core CPU E5300 @ 2.60 GHz with 2 Gb of RAM (only LibO is launched on computer). If we stop trying to scroll through a document, CPU use drops significantly to 10% or even less after some time. The more pages contains document, more freezes we see. Apache Open Office 3.4.1 Writer AOO 3.4.1m1 (Build: 9593) - Rev. 1372282 open and scroll this document in any direction with significantly fewer delays (CPU use jumps max to 50% and rapidly falls to zero) on Russian Windows XP Professional SP3 (32bit)
Verified on 3.6.3.2 - changing version to reflect this. Marking as: New (confirmed) Major (major CPU usage, slows down entire system) Medium (default for major, I think because this is rtf which isn't affecting many users, loweing to Medium is appropriate). Thanks for reporting
AOO 3.4.1 is not the ancestor of LO 3.6, so this bug can't be a regression from AOO. Changed summary accordingly. That said how this file has been produced? The table is not a true table but is build by joining frames. I suspect another problem with a RTF file produced by Crystal Report or some software like that. Best regards. JBF
(In reply to comment #2) > The table is not a true table but is build by joining frames. > I suspect another problem with a RTF file > produced by Crystal Report or some software like that. I agree. It appears to be produced by Oracle Reports: $ head -n 12 Example\ 16.rtf | grep info {\info {\creatim \yr2012 \mo\Aug \dy02 \hr13 \min21 \sec50} {\author Oracle Reports} {\title 8354-1OZFS5A99.rtf} } There are 633 frames in the provided 2-page document in a layout that suggests a table is called for. While this file may be a decent stress test for frame handling I am not sure it is a RTF-specific scrolling issue, as the following indicates. I tested the provided file under Ubuntu 10.04 x86_64 running: - v3.3.0.4 OOO330m19 Build: 6 - v3.4.6.2 OOO340m1 Build: 602 - v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b - v3.6.7.2 Build ID: e183d5b - v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24 - v4.1.4.2 Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72 All versions really struggle with this file. Versions 3.3.0.4 and 3.4.6.2 are near unworkable, taking a long time to refresh the display. 3.5.7.2 is very slow but offers the best performance, while 3.6.7.2 is slower than 3.5.7.2, and both 4.0.6.2 and 4.1.4.2 are slower than 3.6.7.2 (but still much better than the 3.3 and 3.4 series). Saving the provided RTF as an ODT under 3.3.0.4 shows a marked improvement in performance for subsequent handling (perhaps to something better than 3.5.7.2 levels of the original RTF). Saving the provided RTF as an ODT under 4.1.4.2 shows little or no improvement in performance for subsequent handling. Summary amended for clarity. Version set to Inherited From OOo.
I suggest to close this bug report as NotOurBug because Oracle Report developers did a bad job (using frames instead of a true table) and it not the job of LibreOffice developers to fix that. Best regards. JBF
Sorry, but LibreOffice developers did a bad job too. Any version of Apache Open Office from [3.4.1 m1 (Build: 9593) Rev.1372282] till [4.0.1 m5 (Build:9714) Rev.1524958] is several times faster with that particular document. It is clear that LibreOffice and OpenOffice projects are too far apart, but some optimizations will not hurt LibreOffice.
Confirmed:4.3.0.0a0+:OSX Version: 4.3.0.0.alpha0+ Build ID: cbe7ab3d6188e725414cbb15ca534f96fe51d8c7 TinderBox: MacOSX-x86@49-TDF, Branch:master, Time: 2014-01-12_00:08:19 Takes a while to open and get the spinning beachball-pizza of death on OSX. LO becomes unresponsive, CPU goes up and I force quit the madness.
** 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 on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
LibreOffice Version: 4.4.2.2 Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6 Locale: ru_RU on Windows XP SP3 Russian Problem still present, but in that version while scrolling "CPU Use" jumps till maximum 55% on Pentium Dual-Core CPU E5300 @ 2.60 GHz with 2 Gb of RAM (only LibO is launched on computer). If we stop scrolling document, "CPU Use" drops to 0% in about 10 sec.
The example file blocked my LibO for 17 minutes until I killed the program. Couldn't open that file with my Intel Xeon CPU on Win 10 Pro, CPU load around 5-20% all the time. Version: 5.3.2.2 Build ID: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1 CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Layout Engine: new; Locale: de-DE (de_DE); Calc: CL
Readable with: Version: 6.0.0.0.alpha1 (x64) Build ID: c1d1f859b268f650143d48f294999cda0fa57350 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: es-ES (es_ES); Calc: group 634 frames in the file (navigator). No blocked or crash but very slow to scroll or to do anything else.
** 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
Version: 5.4.7.2 Build ID: c838ef25c16710f8838b1faec480ebba495259d0 CPU Threads: 2; OS Version:Windows 5.1; UI Render: default; Locale: ru-RU (ru_RU); Calc: group No changes, problem still present (as it was in Version: 4.4.2.2)
Dear Timon, 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
Version: 6.3.3.2 (x64) Build ID: a64200df03143b798afd1ec74a12ab50359878ed CPU Threads: 4; ОС:Windows 10.0; UI Render: GL; VCL: win; Locale: ru-RU (ru_RU); Calc: threaded Problem still present. Even file opening itself takes a long time, "Not responding" message appears, memory usage constantly around 27% on i3-8100 CPU @ 3.60 GHz with 8 Gb of RAM. LibreOffice at that time is near unworkable, taking a long time to refresh.
Repro 7.2+. Another example is DOC created as RTF in Crystal Reports, attachment 78882 [details] from bug 64240.
Still repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 47a8a65022e3fd7624c95d0341b4809aad11fddb CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded
Dear Timon, 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 repro in Version: 7.6.3.2 (X86_64) / LibreOffice Community Build ID: 29d686fea9f6705b262d369fede658f824154cc0 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded No changes are felt. Even file opening itself takes a long time, "Not responding" message appears, memory usage constantly around 27% on i3-8100 CPU @ 3.60 GHz with 8 Gb of RAM. LibreOffice at that time is near unworkable, taking a long time to refresh.