Created attachment 156135 [details] One page, two tables, very very slow rendering The performance of table rendering is so bad -- appalling -- that Writer is very nearly unusable when tables are involved. Calc is somewhat faster but can still be slow. I will attach a typical form from my school. On my system, it takes at least 5-15 seconds for anything to display. It's a *one-page document*. 5 seconds to render one page on a modern computer system is ludicrous. Scrolling through the document also shows severe performance degradation -- not quite as bad, but from a workflow perspective, it means: if you used the scroll wheel, you will probably overshoot and have to go back (more delays), or you had better use pageup/pagedown *one key press at a time*, waiting 1-2 seconds every time. Also, I believe there are spurious rendering requests being issued. To close the document requires 5-10 seconds before it disappears. What is it doing in that time? There is no need to process anything for display, for something that is very shortly not going to be displayed! Same for "Save as" -- delays both before and after saving...??? Why? I have tried toggling OpenCL/hardware acceleration options. Nothing helps. High CPU usage during all of these delays. As a further test, today I upgraded from 6.1.something to 6.2.8 and my general impression is that somehow 6.2.x has degraded the performance *even further*. (5+ sec for 6.1.x, 10-12+ sec for 6.2.x.) Multiple users have complained about this over many years (e.g. may be similar to #125171, #120360 for Draw), but it has never improved. Ubuntu 18.04.
Hi there I can't really confirm on my computer, using LO 6.3 and 6.4 and Ubuntu 18.04 (with Budgie as the desktop environment). My laptop hs 16 GB of Ram, but the soffice process stays below 150 MB, which seems reasonable. In my tests, it takes about 3 to 4 seconds to open the document and for the UI to be rendered completely, and scrolling is smooth. Closing the document is pretty much instantaneous. The 6.2 branch will not see further development. Would you mind trying the latest release of the 6.3 branch? Tested on: Version: 6.3.3.2 Build ID: 1:6.3.3-0ubuntu0.18.04.1~lo1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-GB Calc: threaded and Version: 6.4.0.0.alpha1 Build ID: cc57df8f942f239d29cb575ea5a7cb01405db787 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded
Dear James Harkins, 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
Dear James Harkins, 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-FollowUp