Description: No apparent pattern to this, but editing documents (length of 90 or so pages in this case), Writer freezes, then crashes, losing all recent edits, even upon recovery. This instability has haunted the last couple of versions (I am using the latest 7.5.1.2). Switching auto-spell checking off improves it, but does not eliminate it. There are a lot of ignored spellings in this technical document, not sure if relevant. There are tables and a coupld of photos as well. It relies on auto and manual page breaks, depending upon content. "Feels" pretty consistent once it goes - the time between the freeze and the crash on this system is about 3seconds. Steps to Reproduce: Just get on with editing/typing work, but when it goes, it goes. Usually extending the document at the end, and editing typos as I go, by hand. Actual Results: It just freezes - no mouse or keyboard possible. Crashes app. Restart. Document recovery process. Document reverts to last saved state. Expected Results: Ideally, no freeze and no crash, please! Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-GB Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no
Thank you for the report, David. Could you please: - paste here the information about your version here, copied from Help > About LibreOffice - if possible, share a document that can help reproduce the issue (with personal information removed) as an attachment to this report ("Add and attachment" link) - test the upcoming version, 7.5.2, to see if it improves things: https://www.libreoffice.org/download/download-libreoffice/?type=deb-x86_64&version=7.5.2&lang=en-US Thank you!
As requested: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL threaded I have now downloaded pre-release 7.5.2 x64 version, and will report back. This has applied to several documents of this kind of length. They are confidential/"internal use only" in nature, and may not be shared. Apologies in that. Thanks for a quick response.
Thank you. It would be also good to test with Help > Safe Mode to see if the issue is linked to Skia/Vulkan (the "UI Render" in your version information). It might be that the issue doesn't happen with Skia turned off. If that's the case, please share the information from your Skia log, which might be in a directory like AppData\Roaming\LibreOffice\4\cache\skia.log (depending on how LibreOffice was installed).
Dear david.c.day, 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 david.c.day, 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