macOS & Intel MacBook Pro crashing regularly while using Lightroom Classic

[AdamWoodworthPhoto]

Ever since upgrading to macOS 13.2.1 and Lightroom Classic 12.2, my computer crashes regularly while using Lightroom Classic. It will crash randomly, often when adjusting sliders, but it just crashed when I was browsing images in grid view.

I am using a 2019 15-inch MacBook Pro, 2.4GHz 8-core Intel Core i9, 32GB RAM, Radeon Pro Vega 20 4GB VRAM. I have 3 external monitors connected and the MacBook screen open as well.

I'm pasting in the crash log that showed up after the reboot caused by the crash that just happened.

panic(cpu 1 caller 0xfffffff028651b08): x86 CPU CATERR detected
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 20P3045
macOS version: 22D68
Kernel version: Darwin Kernel Version 22.3.0: Thu Jan 5 20:17:53 PST 2023; root:xnu-8792.81.2~1/RELEASE_ARM64_T8010
KernelCache UUID: 66D3D9EAC3796DA60EBA5A1BCB588E81
Kernel UUID: A133ECF3-E2EF-3DEA-8A4C-D21463BB0B0D
Boot session UUID: 1EB40C9E-EBAE-4F6E-908D-8077EF11CE1E
iBoot version: iBoot-8419.80.7
secure boot?: YES
roots installed: 0
x86 EFI Boot State: 0x16
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0x1
x86 Previous Power Transitions: 0x70707060400
PCIeUp link state: 0x89271611
macOS kernel slide: 0x17400000
Paniclog version: 14
Kernel slide: 0x0000000022300000
Kernel text base: 0xfffffff029304000
mach_absolute_time: 0x33d33312be1
Epoch Time: sec usec
Boot : 0x63ffd8c2 0x00002615
Sleep : 0x00000000 0x00000000
Wake : 0x00000000 0x00000000
Calendar: 0x64021c61 0x000f31ba

Zone info:
Zone map: 0xffffffdc2b418000 - 0xffffffe22b418000
. VM : 0xffffffdc2b418000 - 0xffffffdd11a7c000
. RO : 0xffffffdd11a7c000 - 0xffffffdd5e748000
. GEN0 : 0xffffffdd5e748000 - 0xffffffde44dac000
. GEN1 : 0xffffffde44dac000 - 0xffffffdf2b410000
. GEN2 : 0xffffffdf2b410000 - 0xffffffe011a78000
. GEN3 : 0xffffffe011a78000 - 0xffffffe0f80e0000
. DATA : 0xffffffe0f80e0000 - 0xffffffe22b418000
Metadata: 0xffffffdc299ac000 - 0xffffffdc2b1ac000
Bitmaps : 0xffffffdc2b1ac000 - 0xffffffdc2b408000

TPIDRx_ELy = {1: 0xffffffe01202b938 0: 0x0000000000000001 0ro: 0x0000000000000000 }
CORE 0: PC=0xfffffff029522848, LR=0xfffffff029522848, FP=0xffffffe22d60ff00
CORE 1 is the one that panicked. Check the full backtrace for details.
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Panicked task 0xffffffe0f8065638: 0 pages, 224 threads: pid 0: kernel_task
Panicked thread: 0xffffffe01202b938, backtrace: 0xffffffe3e569f6c0, tid: 322
lr: 0xfffffff0294f144c fp: 0xffffffe3e569f700
lr: 0xfffffff0294f125c fp: 0xffffffe3e569f770
lr: 0xfffffff029627220 fp: 0xffffffe3e569f7e0
lr: 0xfffffff0296261b8 fp: 0xffffffe3e569f8a0
lr: 0xfffffff0294b15fc fp: 0xffffffe3e569f8b0
lr: 0xfffffff0294f0cd0 fp: 0xffffffe3e569fc60
lr: 0xfffffff029b9ac1c fp: 0xffffffe3e569fc80
lr: 0xfffffff028651b08 fp: 0xffffffe3e569fcb0
lr: 0xfffffff028639604 fp: 0xffffffe3e569fd10
lr: 0xfffffff028642ac8 fp: 0xffffffe3e569fd60
lr: 0xfffffff02863bb58 fp: 0xffffffe3e569fe00
lr: 0xfffffff028638b94 fp: 0xffffffe3e569fe70
lr: 0xfffffff028455b40 fp: 0xffffffe3e569fea0
lr: 0xfffffff029ae605c fp: 0xffffffe3e569fee0
lr: 0xfffffff029ae58b4 fp: 0xffffffe3e569ff20
lr: 0xfffffff0294bc6c0 fp: 0x0000000000000000

[TheDigitalDog]

Try logging into another Mac user account (you should make a new one); still crashing? 
Try starting up in Safe mode (hold down Shift Key when booting*), still crashing? 
You might want to try running a free utility like Onyx: still crashing? 
https://www.titanium-software.fr/en/onyx.html
Also view:
https://www.macworld.com/article/352902/onyx-review-macos.html
https://www.macworld.com/article/224955/how-to-reset-a-macs-nvram-pram-and-smc.html
From Adobe:
https://helpx.adobe.com/photoshop/kb/basic-troubleshooting.html

* How to start your M1 Mac in Safe Mode
On your Mac, choose Apple menu () > Shut Down.
After your Mac shuts down, wait 10 seconds.
Press and hold the power button until the startup disks and Options appear.
Press and hold the Shift key, then click Continue in Safe Mode.

[Ian Lyons]

Your bug report is highlighting a 'kernel panic'. These are almost always related to hardware or driver issues rather than any particicular application. 

https://support.apple.com/en-gb/HT207359

and

'The kernel_task process is at the core of macOS, and it includes a variety of low-level functions that allow the computer to work. One of its primary functions is ensuring your Mac doesn't overheat.'

[Ian Lyons]

A Google search using the 'Kernel Version' from your logs produces this list on Apple's Community Forum (Kernel version: Darwin Kernel Version 22.3.0: Thu Jan 5 20:17:53 PST 2023; root:xnu-8792.81.2~1/RELE...)

[AdamWoodworthPhoto]

This seems to be related to having 3 or more monitors connected in my case. If I disconnect my third monitor then I do not experience the crashing.

[TheDigitalDog]

If only LR is crashing with that third display, do file a bug report for Adobe.

Photoshop:

https://community.adobe.com/t5/photoshop-ecosystem-bugs/how-do-i-write-a-bug-report/idi-p/12373403

Lightroom:

https://community.adobe.com/t5/lightroom-classic-bugs/how-do-i-write-a-bug-report/idi-p/12386373

[Ian Lyons]

I very much doubt this is an issue that Adobe can fix. 

The OP is using a 2019 15-inch MacBook Pro, 2.4GHz 8-core Intel Core i9, 32GB RAM, Radeon Pro Vega 20 4GB VRAM. These and the 16-inch were renowned for over heating when external monitor was connected. Two monitors with 4GB of VRAM is pushing the limits and clearly three tips the GPU over the edge.

As I wrote above "The kernel_task process is at the core of macOS, and it includes a variety of low-level functions that allow the computer to work". One of its primary functions is ensuring your Mac doesn't overheat.'"

[TheDigitalDog]

If only Lightroom Classic is crashing with three displays, someone at Adobe should be looking into this. 

[Ian Lyons]

I don't believe it's Adobe's issue to look into, but while waiting for Adobe to look into I would be trawling the Apple an other Mac related forums for similar issues. In this case, it will be very easy to find them.

The OP's crash report contains the line "panic(cpu 1 caller 0xfffffff028651b08): x86 CPU CATERR detected. That line is a red flag that should not be ignored - "CATERR" is CATastrophic ERRor and is usually a hardware issue. Sometimes, it's on the logic board an on others a peripheral (or the cable conecting the perpheral).  A Google search will turn up dozens of examples. Below is only one of many examples pointing to the display adapter.