I have had two kernel panics while building in Xcode, or running extremely simple interactions with a single Swift Double in playgrounds in Xcode. Has any one else seen this while building in Xcode?
For whatever it is worth, Gemini states it is not a hardware problem, but something to do with "aggressive memory security protocols to support modern unified architectures and stricter platform boundaries", and that this is a an assertion error in Darwin.
Given that this happened twice over the last three days, I'm a little concerned.
Thanks in advance
Hardware: M5 Max with 129 GB, and ~720 GB of storage
First incident configuration (while building in Xcode):
Xcode: 26.5 MacOS: 26.5.1
Second incident configuration (while running a playground in Xcode):
Xcode: Version 26.6 (17F113) MacOS: 26.5.2
Second incident (looks like an underflow in Core 0):
"bug_type":"210", ...,
"os_version":"macOS 26.5.2 (25F84)",
"roots_installed":0, ...
"product" : "Mac17,6",
"kernel" : "Darwin Kernel Version 25.5.0: ...
"socRevision" : "11",
"panicString" : "panic(cpu 0 caller 0xfffffe0051dde6fc):
vm_object_activity_end(0xf3fffe14df4d2e00):
underflow ...
@vm_object_internal.h:700
Debugger message: panic
Memory ID: 0xff
OS release type: User
OS version: 25F84
Kernel version: Darwin Kernel Version 25.5.0: ...
Exclaves boot status: BOOTED_EXCLAVEKIT
Fileset Kernelcache UUID: 5311854233360499876BA3DD5FD3C710
Kernel UUID: BEA0911B-FF13-3AE9-816D-8DEF9DD951DF
...
roots installed: 0
Paniclog version: 15
CORE 0 is the one that panicked. Check the full backtrace for details.
CORE 1: PC=0xfffffe0051d5e7e0, LR=0xfffffe0051e5dc3c, FP=0xfffffecffaf33af0
CORE 2: PC=0xfffffe0051d14b6c, LR=0xfffffe0051d14b6c, FP=0xfffffec34a8f7ee0
...