Description: I have a sensitive document that won't be distributed that if I click the AutoFilter icon in the top bar, it consistently crashes. Same thing in Safe Mode. MacOS does not pick up that LO crashed, so I don't have crash data available but can do a trace or grab data from relevant file as advised. Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Mac OS X 13.0; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded sw_vers ProductName: macOS ProductVersion: 13.0 BuildVersion: 22A380 sysctl -n machdep.cpu.brand_string Apple M1 Steps to Reproduce: SEE DESCRIPTION Actual Results: SEE DESCRIPTION Expected Results: SEE DESCRIPTION Reproducible: Always User Profile Reset: Yes Additional Info: SEE DESCRIPTION
Created attachment 183526 [details] locrash.png Screenshot showing a crash happened with Calc.
Hi Christopher This will be very hard for us to test, without a log or a document to use to test. Would you be able to modify the document so it doesn't contain sensitive information anymore but still reproduces the crash?
Hi Stéphane Guillou (stragu), Thanks for the quick response! For now, while I'm not going down the rabbit hole of document carving, if you advise which log you want, and/or provide fully detailed step-by-step instructions on gathering debugging log for macOS (not ahead of this) I don't have a problem providing. There is nothing logged in console about a crash, otherwise would have already posted.
Created attachment 183544 [details] sudo dtruss -n soffice.txt Opened file, started dtruss, reproduced crash, and then created this attachment.
Thanks Christopher Please the section about macOS here: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#macOS Note this sentence: "NB: Depending on your system configuration and user setup, you may or may not be asked about sending a report to Apple; you may need to be logged in as an admin user to see these dialogs." Hopefully that helps? Devs: is the provided attachment 183544 [details] of any help?
Hi Stéphane, thanks for the link, but there are a few problems with it: 1) Not all application crashes are guaranteed to be caught by Apple's built-in crash reporter. The article is written as if it does. 2) It implies there is a way to gather crash logs outside of Apple crash reporter with full debug symbols, but provides no details on how to do so. 3) Unfortunately, it adds nothing new to this report. As mentioned in the Description, macOS does not pick up that LO crashed.
Hi Christopher Thank you for the reply. - Could you please try the latest master build to see if the issue persists? https://dev-builds.libreoffice.org/daily/master/current.html - Have you witnessed the issue in previous versions or did it start with 7.4.2.3 ? Or maybe with an upgrade to macOS 13?
Hi Stéphane Guillou (stragu), Thanks for the follow up. (In reply to Stéphane Guillou (stragu) from comment #7) > Hi Christopher > Thank you for the reply. > - Could you please try the latest master build to see if the issue persists? > https://dev-builds.libreoffice.org/daily/master/current.html There are no MacOS aarch64 builds for master to test with. > - Have you witnessed the issue in previous versions or did it start with > 7.4.2.3 ? I don't recall testing to this precise issue in earlier LO versions. > Or maybe with an upgrade to macOS 13? I don't recall testing to this precise issue in prior OS versions.
Hi again Christopher You should now be able to see aarch64 builds: https://dev-builds.libreoffice.org/daily/master/current.html
Tried with latest and didn't reproduce, but I had been making changes on the master file all along the way. Hence, marking as WORKSFORME as I'm not investing any further time into this. If I can reproduce I'll file a new report.