It happened at random. At some point auto-save just started endlessly looping, and after plenty of minutes I had to terminate it. The document then was destroyed. For the record its size was 360MB. It could be that the bug has been there for plenty of time, as there are many potential duplicates: Endless autosave loop https://bugs.documentfoundation.org/show_bug.cgi?id=95151 Loop in autosave https://bugs.documentfoundation.org/show_bug.cgi?id=113344 autosave locks program into continuous loop https://bugs.documentfoundation.org/show_bug.cgi?id=106032 If you need the document email me for it, as this bug-tracker hangs while uploading it.
Arch Linux, libreoffice-fresh 6.3.4-1 I've also experienced this issue twice in the past 2 weeks with an ~825K .ods file. (The first version of this file was created in Sep 2018 and I did not experience this issue until Jan 23, 2020.) I believe I've identified the culprit on my system. 2 weeks ago, I re-enabled a thumbnail maintenance cron job which runs weekly. What I didn't realize is that /tmp was filling with 0-byte magick-*.pam files and magick-* symlinks as a result of this script. When I deleted these 0-byte files, Calc completed an autosave and stopped looping. I didn't think to get a count of the 0-byte files, but I strongly suspect the issue is a lack of available inodes in /tmp, since LO also uses /tmp while creating the auto-save. I'm not sure it's within the scope of LO, but perhaps the autosave code should exit and warn the user if LO is unable to create the necessary files in /tmp?
Alberto, please write your OS. Is Kevin's case related to yours?
It could be the same issue, as I'm using Manjaro Linux.
My drive died three months later...
I have the same issue in Impress (I only use Impress, so I don't know if it's present in other components). Version: 7.2.3.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US 7.2.3-1 Calc: threaded
Dear Alberto Salvia Novella, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Probably it would be better if LibreOffice used "~/.cache" instead of "/tmp". I cannot test it, because these days I rarely need to use office suites.