Description: LibreOffice crashes on a Mac when closing some spreadheets, even if nothing has been edited. App needs to be force-closed. At subsequent start LibreOffice offers to recover closed files even though they were not changed at all. Steps to Reproduce: 1.On a Mac: open both attached spreadheets, do not edit anything 2.then first close "BDR-left.ods" 3.then close "BDR Android - Worklog.xlsx" 4.LibreOffice crashes Actual Results: LibreOffice crashes Expected Results: LibreOffice closes normally Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.2.5.2 Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU threads: 4; OS: Mac OS X 10.13.6; UI render: default; VCL: osx; Locale: de-DE (en_DE.UTF-8); UI-Language: en-US Calc: threaded Happens since LO 5.x with some spreadsheets. OpenGL on/off does not matter. I tried resetting my profile multiple times.
Created attachment 153194 [details] ZIP file contains 2 spreadheets to reproduce crash when opening and then closing both
No repro for me with Version: 6.2.5.2 Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 Threads CPU : 4; OS : Mac OS X 10.14.6; UI Render : par défaut; VCL: osx; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded I had to open the XLSX file you provided in the ZIP as a copy because when I tried to open it by dragging and dropping onto the LO Dock icon, I got an error message indicating that the file was locked for editing by you. Closing each file in the order you specified didn't lead to a crash. I would guess that your XLSX file has something particular about it which is causing the crash.
Opening the XLSX file in Excel for Mac 16.27 (19071500) takes a very long time for a 21kb file. It appears that there are lots of ambiguous date strings in column A, at least, Excel flags them up and offers to correct them. Could this be the cause of the issue you are experiencing ? Further playing around with both files (loading / closing, in different orders) in LO doesn't cause a crash on my system.
Can not confirm crashes opening either file with LO 6.3.1.2. Version: 6.3.1.2 Build ID: b79626edf0065ac373bd1df5c28bd630b4424273 CPU threads: 8; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; Locale: de-DE (de_DE.UTF-8); UI-Language: en-US Calc: threaded @Ernst: Can you install 6.3.1.2 and see if it crashes for you please.
Dear Ernst42, 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 Ernst42, 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