Hello, if I want to open large drawing files (.odg), then the CPU stick at 100% load (for over 5 minutes, then I stop Libre Office). If I remove half of the objects from the large file, then at the beginning for 20 second Libre Office Draw has 100% CPU, but then it works normal. When sticking at 100% I can see the document and the preview, select objects, but editing is impossible, because of the slow windows behaviour. I have attached two documents. One with the half number of object without sticking and the other with the number that starts the sticking. I have noticed this beviour first at Libre Office 4.0. and also version 4.3 is showing the sticking. The Version 3.6 is not showing this behaviour and works fine, even with large files. I have noticed this behaviour under OS Window and Linux on two different computers. Can someone fixed this? Kind regards
Created attachment 106010 [details] one file only because of >3MB I add only one odg file (>3MB), which makes the problem 100% CPU, if you remove half of the objects, all is fine an the CPU load goes down, at least when you reload the file.
(In reply to Rüdiger Arnold from comment #0) > Hello, > > if I want to open large drawing files (.odg), then the CPU stick at 100% > load (for over 5 minutes, then I stop Libre Office). > If I remove half of the objects from the large file, then at the beginning > for 20 second Libre Office Draw has 100% CPU, but then it works normal. TESTING with LO 4.3.2.2 + Ubuntu 14.04. NO REPRO with the given sample ODG. It opened within 10 seconds in Draw, and was editable from the very beginning. Status -> RESOLVED WORKSFORME Rudiger: If you're still experiencing this problem with the latest builds of 4.3, please let us know what version of LibreOffice and Windows or Linux distro you're using.
(In reply to Robinson Tryon (qubit) from comment #2) > (In reply to Rüdiger Arnold from comment #0) > > > > NO REPRO with the given sample ODG. It opened within 10 seconds in Draw, and > was editable from the very beginning. > Yes the attached document is editable from the early beginning, but the CPU power sticks at 100% CPU power after opening the file. Tryon: Would you be so kind !to check the CPU power and give me feedback! after opening my attached document. If you have a powerful hardware (several cores), may be you notice the slowing down. I have a netbook. > > Rudiger: If you're still experiencing this problem with the latest builds of > 4.3, please let us know what version of LibreOffice and Windows or Linux > distro you're using. I tried with also with 4.3.4 The same effect. My System Window 7 Starter, SP1, 32 Bit Netbook AMD Athlon II Neo K125 Processor 1.7 GHz RAM 2GB Thank you for your Feedback Rudiger
(In reply to Rüdiger Arnold from comment #3) > Yes the attached document is editable from the early beginning, but the CPU > power sticks at 100% CPU power after opening the file. > > Tryon: Would you be so kind > > !to check the CPU power and give me feedback! TESTING with LO 4.4.0.0.alpha2 + Ubuntu 14.04 (AMD64) > after opening my attached document. After opening, the soffice process stayed very reasonable. It perhaps hit 13% CPU and 20% RAM once or twice, but even while clicking on elements, it remained very low, often below 5% CPU usage. > If you have a powerful hardware (several > cores), may be you notice the slowing down. I have a netbook. My test machine: - Intel® Core™2 Duo CPU T8300 @ 2.40GHz × 2 - 4GB RAM - GeForce 8600M GT/PCIe/SSE2 > I tried with also with 4.3.4 The same effect. > > My System > > Window 7 Starter, SP1, 32 Bit > Netbook AMD Athlon II Neo K125 Processor 1.7 GHz > RAM 2GB It could be a windows-only problem...I'll make a note to test it with Win7. (Status REOPENED is reserved for bugs that have been marked as FIXED Status -> UNCONFIRMED)
Windows test results on a machine with about the same specs as in comment 4: 10 secs to open, CPU peaked at 25%. Win 7 64-bit 4.3.4.1 and Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
I can confirm with LO 4.3.4.1, win7. When I open file then process soffice.bin loads CPU ~25% (intel i5), but this value is still, even if I do nothing with the file. Looks like some loop.
Migrating Whiteboard tags to Keywords: (perf)
** 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 (5.1.6 or 5.2.3 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
No repro with: Version: 6.0.0.0.alpha0+ Build ID: c5a93cad149618bbd43632f1660a558c34bdbf7e CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-10-07_01:04:25 Locale: nl-NL (nl_NL); Calc: CL
Created attachment 137307 [details] Callgrind output from 6.0 I think the point is, like raal said in comment 6, that the CPU stress remains constant even though nothing is done to the document. This is still true. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha1+ Build ID: 02a3abcceeb9be7f101b0bcaf55accc7fb6bfcf7 CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on October 26th 2017
(In reply to Buovjaga from comment #10) I'm not seeing any CPU stress with: Version: 6.0.0.0.alpha1+ Build ID: b17294826830e278d060c876cf4f94a9b4ec16cc CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-10-23_06:32:42 Locale: nl-NL (nl_NL); Calc: CL nor with Ubuntu 14.04 GTK2 with 5.4.1.2 or 6.0.0.0Alpha1
Well, for me on Win 10 the CPU for soffice was hovering between 7% and 16% without doing anything.
(In reply to Buovjaga from comment #12) > Well, for me on Win 10 the CPU for soffice was hovering between 7% and 16% > without doing anything. I can reproduce it now. It's only happening with Automatic spell Checking enabled Version: 6.0.0.0.alpha1+ Build ID: b17294826830e278d060c876cf4f94a9b4ec16cc CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-10-23_06:32:42 Locale: nl-NL (nl_NL); Calc: CL
Oh look people I fixed this without even knowing I did: https://cgit.freedesktop.org/libreoffice/core/commit/?id=e208b81540d43e2b7d3012dfe6bebc59ce638c12 https://cgit.freedesktop.org/libreoffice/core/commit/?id=814e50e6622ea9701094f3ec309a395d175c494f It's fixed in 6.1 for sure, IDK about 6.0 though