Description: When trying to save an already existing ODP document with Impress, it often "freeze" while saving it, taking many minutes to finish. dmesg shows no error (empty since booting), apparmor reports unconfined attempts (that I choose to report) . top reports soffice.bin with 13.2Gb Virt Mem occupied 100%CPU (load avg 1.5 with no other tasks running), on a Ryzen 5 3600 with 32Gb RAM 1Tb Nvme SSD strace -p , reports not any output until soffice.bin finaly "unfreeze" and save the document. I can provide the document (private) that leads to freezing. Tried on LOO 6.2.8.2-2 , 6.3.3, 6.3.4.2 Steps to Reproduce: 1. Open the document 2. Edit/ Modify one Slide 3. Save the document Actual Results: Freeze and high memory and CPU load After "recovering" the very long freeze (more than 10 minutes), I can Save As the document same location other name , without ANY freeze... Using and saving this new document generates the same freeze (the more you save the longer the freeze behaves). Expected Results: Just save and give back hand to modify the document. Reproducible: Always User Profile Reset: Yes Additional Info: Ubuntu 19.10 Linux chryjs-B450-AORUS-PRO 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I do NOT reproduce it on another computer with Ubuntu 19.04 and Intel i7-6500/16 Gb RAM 1TB SSD I can provide more information if required
More investigations : It seems that previous LOO release are not affected up to 6.1.6.3 (included); The CPU load is only affecting 1 thread which load level reach 100% during this "freeze". The other threads are not affected (which seems logical), their load remains under 10% the 11 other ones. dmesg, syslog, kern.log remains empty of related messages.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Is this still an issue in 6.4.4
Dear chryjs, 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 chryjs, 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