Created attachment 167422 [details] Corona Statistics The attached spread sheet frequently crashes after saving during closing.
I've tried to play with the document and I saved it many times (in the order of tens) and it works good for me. Version: 7.1.0.0.alpha1+ (x64) Build ID: 418c63dff5db2005bbc4dbfc92b56778f89cea8b CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: en-GB Calc: CL
(In reply to Nick Hildebrand from comment #0) > Created attachment 167422 [details] > Corona Statistics > > The attached spread sheet frequently crashes after saving during closing. can you write here step by step your actions that give a crash?
I do the daily updates of the Corona figures, press the icon save, wait until the progress bar ends and then press the red X in the upper right corner. The result is the message: LibreOffice 7.0 Dokumentwiederherstellung Durch einen Fehler ist LibreOffice abgestürzt. ..... Die folgenden Dokumente werden wieder hergestellt: The window with the list of documents is empty. The Task Manager shows LibreOffice 0% CPU Load and 166MB RAM usage The only way to come over the blocking is to end the Task in the Task Manager,
[Automated Action] NeedInfo-To-Unconfirmed
Thank you for reporting the bug. I made few changes in spreadsheet, saved during closing, It does not crashes. I can not reproduce the bug in Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Version: 7.2.0.0.alpha0+ (x64) Build ID: 761a672d62df1891b9f4f367a499b220ab2b33fa CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Thanks for reporting this issue. Could you please paste the info from Help - about LibreOffice ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the information has been provided
Dear Nick Hildebrand, 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
Hi Nick, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Nick Hildebrand, 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