So if you can’t enable OpenCL, please try updating the graphics driver.
“Try updating the graphics driver”. My Mac is up to date. LO is up to date. How would I go about updating a graphics driver?
“First steps to take before submitting a bug…”
Thanks, but I haven’t got a bugzilla account so I can’t submit a bug.
I don’t know Mac, but with Windows sometimes updating drivers directly from the vendor have solved issues for me.
The vendor is Apple. I don’t think that drivers can be updated in the same way that they can on Windows or Linux machines. Thanks for trying to help, though.
Apologies to the OP osxtra - it feels like I’ve hijacked your thread and that wasn’t my intent.
No worries. I now do have a feeling it’s graphics related, and Mac specific. Tested 24.2.4.2 on a Windoze machine (10 v22H2), and a *nix box (Fedora 40), both Intel graphics, no apparent issues.
FWIW my OS is Ventura but I’m still running an old nVidia Titan Black card, which is now about 10 years old, running Metal 2 (not latest 2.2 so, for example, latest Blender won’t run); no way to update drivers thanks to the Fruity company dropping nVidia.
Am sticking with 24.2.3.2 on the Mac for now.
Also not meaning to hijack the thread, but on the subject of logging am not sure where to look for info on crashes, except for system logs. On the Mac, haven’t found any LO specific logs in the user profile folder, except for “skia.log” in cache which doesn’t seem to contain useful info.
Would be nice to know why 24.2.4.2 is crashing on the Mac, but as the previous tick is not, it’s a bit of a mystery. Will crank up the latest version again during some free time for more testing…
Apologies if you know, but you can run Mac’s Console utility to log messages, errors and faults and then hope that LO crashes while its running. Console will also have logs of serious crashes that’s searchable. I’ve not found anything useful for my crashes, but yours might show up. TBH I don’t find Console very much use unless you know precisely what you’re looking for. Good Luck!
Thanks, am aware, should have been more clear when I said “system logs”.
And you’re right, they can be rather cryptic. Nothing stood out last time I looked, but will look again next time it crashes…
I am getting the crashes with Calc - 5 in 5 minutes with the first spreadsheet i created on my new mac with Sonoma. Just cutting and pasting.
No crash report generated: Crash Report Tool
Just restarts with the recover file dialog box.
Sorry for the delay in replying. Same as what @aandolan reported. No crash reporter, just the recovery screen.
FWIW had switched back to 24.2.4.2 after reading your reply and this was the first crash since then. Not sure if this is relevant, but this time it was after opening a CSV in Calc and attempting to copy & paste some cells from one place to another. Have had other .ods docs open - both brand new and existing - without it crashing.
OpenCL is not used per Preferences.
For me the same issue appears in macOS Sonoma 14.5 on a 16-inch 2019 MacBook Pro with Intel Processor, AMD Radeon Pro 5500M and Intel UHD Graphics 630.
I can start from a fresh spreadsheet, I don’t even need to save it or add any content. Just copying empty cells and cell ranges at random in the first 5x5 grid of cells will lead to the crash. I don’t need to paste. It happens within the first 30 copies usually.
It seems to happen much quicker if my mouse movements are sloppy. Like I happen to copy with command+c but my cursor is still moving, maybe? Or my selection wasn’t fully ready when I copied? Maybe it’s some sort of race condition between the selection changing and the copy starting…
Version: 24.2.4.2 (X86_64) / LibreOffice Community
Build ID: 51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2
CPU threads: 16; OS: macOS 14.5; UI render: Skia/Raster; VCL: osx
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded
Ah I found a surefire way to reproduce it in just three copies! Starting from an empty spreadsheet in a freshly started libreoffice process:
- select A1, press command+c,
- select B1:C1, press command+c
- select D1, press command+c
That leads to an instant crash. And I don’t even need a mouse, this works with keyboard selection of the fields as well.
Copying only single cells repeatedly seems to be safe, copying only ranges repeatedly also, but as soon as you copy a single cell after previously copying a cell and then a range, it crashes.
Thanks everyone.
macOS crashes associated with copying cells in Calc have affected many users. The issue appeared in 24.2.4 and is tracked in 161461 – Crash on second copy after pasting using Enter in Calc on macOS
A fix is already released in the current mac app store version, and available in the upcoming version 24.2.5.
You can already get the pre-release of 24.2.5: Download LibreOffice | LibreOffice - Free and private office suite - Based on OpenOffice - Compatible with Microsoft
I too experienced this issue Mac M2 here, up-to-date software. However I reverted back, and then re-installed 24.2.4 and was not able to recreate the bug. However, I opened the same spreadsheet it had crashed on, copied and pasted the same formula, and it didn’t crash. Odd.
Stragu,
Thank you for your good and positive comment. Appreciated.
Jan
I have tried both 24.2.5.2 and downgrading to 24.2.4 and the problem with crashing while copying cells is still present in both. Using a M2 Mac Mini running Sonoma.
EDIT: downgrading to 24.2.3, this also crashes!
??? What is “pedantic” here? Did you try to follow the link, and try to understand what was proposed to you? The bibisect procedure is a way to find out a specific code change that started the problem - something that helps to find out the reason for the change, and to fix that…