Description: After some time (15 minutes to half an hour?) soffice.bin process starts to eat 100 % of cpu time (as seen with UNIX's top utility). It stops after I save a document that is open. Autosave does not stop it, only the save command from the user. The problem appears even if the user just starts an empty write document and waits long enough (also if older document is opened). I have not any special settings turned on. LibreOffice version: 6.1.5.2. Kernel 4.19.118 hardware: Raspberry Pi 4, 4 GB OS: Raspbian (Raspberry Pi OS), 32-bit, based on Debian buster Exactly the same problem appeared on IBM T43 computer with Slackware 14 (32-bit cpu, 2 GB mem) and a bit older LibreOffice version. The problem didn't appear with Lenovo Thinkcentre M55 (a desktop computer released in 2006) and Debian. It looks anyway that the problem appears with some older systems (so far they all have had 32-bit OS though RPi4 is a 64-bit computer, typically running in 32-bit mode). Steps to Reproduce: 1. Start LibreOffice Writer in a system where the bug appears 2. Wait for 15 minutes to half an hour or so while keep on watching CPU usage 3. Actual Results: office.bin process eats all the CPU that is available Expected Results: Writer without activity should not use barely any CPU Reproducible: Always User Profile Reset: No Additional Info: Version: 6.1.5.2 Build ID: 1:6.1.5-3+rpi1+deb10u6+rpt1 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group threaded
LibreOffice 6.1 isn't outdated and not supported anymore; Please use 6.4 or ideally even LibO 7.0
Sadly, the version I'm using is the latest that can be found from Raspberry Pi OS's repository
(In reply to jsihv from comment #2) > Sadly, the version I'm using is the latest that can be found from Raspberry > Pi OS's repository try ask maintainers to update LibreOffice in their repo
> LibreOffice 6.1 isn't outdated and not supported anymore; Please use 6.4 or ideally even LibO 7.0 Set to NEEDINFO accordingly. rimrunner: Please set back to UNCONFIRMED if this bug exists in the newer supported version. Without this information we are not able to identify the issue, especially it's on Raspberry Pi and maybe not on other linux distributions.
Dear rimrunner, 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 rimrunner, 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