(Mac) Kernel panic crash when editing item

abrauer

Several times now, I've had my M1 Macbook hard reboot, seemingly always when editing items. The debug output doesn't seem to catch it, since the whole system crashes. The macOS report starts like this (it's too long for the forum):
panic(cpu 3 caller 0xfffffe00191f921c): Kernel data abort. at pc 0xfffffe00189f9058, lr 0x6ea3fe0018a9169c (saved state: 0xfffffe53bc1432d0)
x0: 0x0000000000000008 x1: 0x0000000000058000 x2: 0x000000003003c5a5 x3: 0x0000000000000000
x4: 0x0000000000000000 x5: 0xfffffe53bc14375c x6: 0xfffffe53bc143768 x7: 0xfffffe53bc143760
x8: 0x0000000000000010 x9: 0x00000000ffdfffff x10: 0x00000000ffcfffff x11: 0x0000000000000000
x12: 0x0000000000420000 x13: 0x00000000004a0000 x14: 0x00000000ffdfffff x15: 0x00000000000003ed
x16: 0x0000020029fb3ef4 x17: 0xfffffe0018ad37f8 x18: 0x0000000000000000 x19: 0x0000000000000008
x20: 0xfffffe14dac2e200 x21: 0x0000000000002000 x22: 0x0000000000000000 x23: 0xfffffe10118a6200
x24: 0x0000000000000000 x25: 0x0000000000058000 x26: 0xfffffe002239def0 x27: 0xfffffe53bc1436f0
x28: 0x0000000000000003 fp: 0xfffffe53bc143650 lr: 0x6ea3fe0018a9169c sp: 0xfffffe53bc143620
pc: 0xfffffe00189f9058 cpsr: 0x60401208 esr: 0x96000005 far: 0x0000000000000010

Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 23A344
Kernel version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: B5B971E36AEB2872B9B570E10D3D2BF3
Kernel UUID: BBDD4971-4AC1-34C9-B0E3-26B569022090
Boot session UUID: B239DA93-1397-4397-9B64-5F6203317640
iBoot version: iBoot-10151.1.1
secure boot?: YES
roots installed: 0
Paniclog version: 14
KernelCache slide: 0x0000000010464000
KernelCache base: 0xfffffe0017468000
Kernel slide: 0x000000001046c000
Kernel text base: 0xfffffe0017470000
Kernel text exec slide: 0x0000000011980000
Kernel text exec base: 0xfffffe0018984000
mach_absolute_time: 0x59deaee7c
Epoch Time: sec usec
Boot : 0x65153241 0x0006ccd0
Sleep : 0x00000000 0x00000000
Wake : 0x00000000 0x00000000
Calendar: 0x65153627 0x000f2304

Zone info:
Zone map: 0xfffffe101189c000 - 0xfffffe301189c000
. VM : 0xfffffe101189c000 - 0xfffffe14de568000
. RO : 0xfffffe14de568000 - 0xfffffe1677f00000
. GEN0 : 0xfffffe1677f00000 - 0xfffffe1b44bcc000
. GEN1 : 0xfffffe1b44bcc000 - 0xfffffe2011898000
. GEN2 : 0xfffffe2011898000 - 0xfffffe24de564000
. GEN3 : 0xfffffe24de564000 - 0xfffffe29ab230000
. DATA : 0xfffffe29ab230000 - 0xfffffe301189c000
Metadata: 0xfffffe1000ab8000 - 0xfffffe1008ab8000
Bitmaps : 0xfffffe1008ab8000 - 0xfffffe100b88c000
Extra : 0 - 0

TPIDRx_ELy = {1: 0xfffffe16797be060 0: 0x0000000000001003 0ro: 0x0000000201283320 }
CORE 0 PVH locks held: None
CORE 1 PVH locks held: None
CORE 2 PVH locks held: None
CORE 3 PVH locks held: None
CORE 4 PVH locks held: None
CORE 5 PVH locks held: None
CORE 6 PVH locks held: None
CORE 7 PVH locks held: None
CORE 0: PC=0x0000000188016984, LR=0x00000001880162f0, FP=0x000000016b54fe80
CORE 1: PC=0x000000018b135ed8, LR=0x0000000192fe9e74, FP=0x000000016d897fe0
CORE 2: PC=0xfffffe0018b1c2bc, LR=0xfffffe0018b2a890, FP=0xfffffe53bb9e3e80
CORE 3 is the one that panicked. Check the full backtrace for details.
CORE 4: PC=0xfffffe0018a17f1c, LR=0xfffffe0018a17f18, FP=0xfffffe53ba19bef0
CORE 5: PC=0xfffffe0018a17f18, LR=0xfffffe0018a17f18, FP=0xfffffe53bc353ef0
CORE 6: PC=0xfffffe0018a17f1c, LR=0xfffffe0018a17f18, FP=0xfffffe53bc3cbef0
CORE 7: PC=0xfffffe0018a17f18, LR=0xfffffe0018a17f18, FP=0xfffffe53bc69bef0
Compressor Info: 6% of compressed pages limit (OK) and 6% of segments limit (OK) with 0 swapfiles and OK swap space
Panicked task 0xfffffe20137f0b38: 571437 pages, 73 threads: pid 2549: zotero
Panicked thread: 0xfffffe16797be060, backtrace: 0xfffffe53bc1429e0, tid: 26576
lr: 0xfffffe00189dd288 fp: 0xfffffe53bc142a70
lr: 0xfffffe0018b36074 fp: 0xfffffe53bc142a90
lr: 0xfffffe0018b26bcc fp: 0xfffffe53bc142b00
lr: 0xfffffe0018b25040 fp: 0xfffffe53bc142bf0
lr: 0xfffffe001898baa4 fp: 0xfffffe53bc142c00
lr: 0xfffffe00189dcb64 fp: 0xfffffe53bc142fb0
lr: 0xfffffe00191ee808 fp: 0xfffffe53bc142fd0
lr: 0xfffffe00191f921c fp: 0xfffffe53bc143150
lr: 0xfffffe0018b26a40 fp: 0xfffffe53bc1431c0
lr: 0xfffffe0018b254d0 fp: 0xfffffe53bc1432b0
lr: 0xfffffe001898baa4 fp: 0xfffffe53bc1432c0
lr: 0xfffffe0018a9169c fp: 0xfffffe53bc143650
lr: 0xfffffe0018a9169c fp: 0xfffffe53bc1437e0
lr: 0xfffffe0018aa62e4 fp: 0xfffffe53bc143970
lr: 0xfffffe0018aa5574 fp: 0xfffffe53bc143a40
lr: 0xfffffe0018aeb6e0 fp: 0xfffffe53bc143a90
lr: 0xfffffe0018a67780 fp: 0xfffffe53bc143ac0
lr: 0xfffffe00189e3b9c fp: 0xfffffe53bc143b60
lr: 0xfffffe00189b7354 fp: 0xfffffe53bc143bc0
lr: 0xfffffe00189cf96c fp: 0xfffffe53bc143c60
lr: 0xfffffe00189cfdd8 fp: 0xfffffe53bc143d50
lr: 0xfffffe0018b1a394 fp: 0xfffffe53bc143e20
lr: 0xfffffe0018b25544 fp: 0xfffffe53bc143f10
lr: 0xfffffe001898baa4 fp: 0xfffffe53bc143f20


dstillman

A kernel panic is by definition a problem with the OS, hardware, or device drivers, not a problem in a user-level app. So this is almost certainly just some bug in Sonoma. With any luck it'll be fixed for you in the next Sonoma update.