Description: I have a graphically rich 8.9 Mbyte file I run my home budget with. Saving the file after working on it takes roughly 4 minutes. Memory usage does not exceed 55% During the save process a process/thread runs one core at 100%, and bounces around which core that is. I frequently get a dialogue box saying Calc is not responding, do I wish to force a close. Imediately then "Saving as" to the back up location takes 20 seconds and the thread only runs on a single core; It doesn't bounce around cores. Varying document format does not change behaviour. Steps to Reproduce: 1. Save a large file EG: My budget spreadsheet of 8.9 MBytes 2. Saving then takes 4 minutes 3. Actual Results: Initial "Save" takes four minutes, subsequent "Save As" takes 20 seconds. Expected Results: Save in under a second, this is what Excel does on the same document. Reproducible: Always User Profile Reset: Yes Additional Info: This has been getting progressivly worse, I assume, as the file grows in size. This is across Linux Mint from 18.0 through to 21.1 including all kernel revisions and all Libreoffice builds, both Flatpak and repository. Fresh installs or upgrades made no difference. The save destination being an SSD, a 10,000 RPM raptor hard drive or USB stick makes no difference.
First, test with the navigator if there is something strange, or unwanted objects. Second, verify you have not unwanted data or formatted cells beyond, the range you want. I any of those works, then please attach a sample file to reproduce the issue. https://wiki.documentfoundation.org/QA/BugReport see description and attachments, on how to clean the file.
Thankyou for your reply, further testing; Saves perform faster after running PROPERTIES Running in safe mode made no difference Resetting properties made no difference Navigator shows 3 OLE objects, aside from SHEETS, all other options are greyed out. The file is my household budget with accounts numbers and transaction details. It will take time to sanitise it before submitting for testing.
[Automated Action] NeedInfo-To-Unconfirmed
I have captured the behaviour with simplescreenrecorder as per below link; https://aussiebroadband-3.wistia.com/projects/l56b2kwuv0
Beautiful, but except you can attach the file, properly anonymized, no way to take a look about what is happening.
we are still waiting your file example
Dear christothemagnificent, 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 christothemagnificent, 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