Description: While typing out a document, at the ten minute mark - LibreOffice attempts to autosave but freezes for 30 seconds and then crashes - with no recovery possible. This has happened three times in a row. Steps to Reproduce: 1.Open LibreOffice to half size screen - Google Docs running in Firefox on other half. 2.Type for ten minutes 3.Crash 4. On Recovery, type recover. 5. Back to last manual save. Actual Results: Back to manual save Expected Results: Autosave and continue Reproducible: Always User Profile Reset: Yes Additional Info: Brand new build - maybe 5 days old? No other programs/problems. Saving to a new file on Desktop using Word Compatible mode. Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL threaded
The only thing that sticks out is Skia/Vulkan for the UI rendering. If you want to experiment, you could deactivate it from Tools - Options - LibreOffice - View - Use Skia for all rendering and then change the autorecovery period to 1 minute temporarily: Tools - Options - Load/Save - General - Save AutoRecovery information every ... minutes
Mike, can you please update to the latest 7.5 version and test again, with and without Skia as suggested by Buovjaga? And does it happen only with a specific document? Setting to "needinfo", please set back to "unconfirmed" when reporting back. Thank you!
Been running it on 7.5.1.2 and hasn't repeated the incident. My theory is that it was attempting a save to a drive that had been playing up at the time and was trying to save over a file that was no longer there - so it crashed out. One of my hard-drives was on its last legs and it formatted itself directly after the incident. Working theory being it couldn't finish the save procedure and soft-locked. (This may be useful in the future, but is no longer a problem)
Thank you for reporting back, Mike. I'll close as "works for me" as you suspect it was a hardware issue, but please set back to "unconfirmed" if it happens again and you can provide some more information. All the best!