Description: Once I open a file software rendering is forced, and the response of LibreOffice draw is "laggy". HOWEVER when I open a fresh-new blank document (thus avoiding loading a file), it is smooth as butter and no performance decline is noticed. I use the term software rendering because when I start moving around geometry in Draw on an opened file, a CPU core goes up to 100%. Likewise as stated above, if I open Draw without loading a file and start manipulating geometry, the CPU core only goes up to 30%. This makes it evident that the latter is using hardware rendering to paint the screen. Steps to Reproduce: 1. Open Draw (do not load file, start with new blank document) 2. Add 6-10 rectangles to the page. 3. Ctrl-A the rectangles and start "shaking them" about the page. Note the CPU usage. 4. Save this document to desktop. Close Draw. Open Draw by double-clicking the document. 5. Preform the same "shaking" to the geometry and notice a slower update rate aswell substantial CPU usage compared to before. Actual Results: After saved and reopened, libreoffice did not use rendering. Expected Results: I expected that sense LibreOffice to use hardware render both before and after the save. Reproducible: Always User Profile Reset: Yes Additional Info: Linux Mint: 18 64-bit Cinnamon: 3.0.7 Kernal: 4.4.0-59-generic Processor: AMD FX 8350 8-Core Memory: 11.6GB Graphics Card: R7 265 Driver: radeon User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/55.0.2883.87 Chrome/55.0.2883.87 Safari/537.36
No perf decline here. Win 7 Pro 64-bit Version: 5.4.0.0.alpha0+ Build ID: c6dd735afb2e1b3837c4f8c5659f52fafab4c56f CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-01-30_01:52:54 Locale: fi-FI (fi_FI); Calc: group
On Linux, when shaking them around I get 60-70% CPU before and after saving & reloading. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: 7ec0500e20cf273d70c4fbddb4063b8f8295307c CPU Threads: 8; OS Version: Linux 4.9; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on February 18th 2016
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180502
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180530