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 ...

After updating to 16.3, my project now fails to compile with the diagnostic: "Command SwiftCompile failed with a nonzero exit code". This is a SwiftUI document project with two local packages, the second of which is a rather large one with 112 SwiftUI files. It is this second package that is failing. There are no issues when compiling with 16.2. Without diagnostics I'm having a bit of difficulty in determining the cause. My thought is to regress the commits unit 16.3 gives a success, or shows issues. Although I'm not catching a similar issue in the forums, I'm seeing other problems with 16.3. Has anyone else had such build failure isolated to 16.3? Any advice on other ways to approach this problem? Thanks in advance

When I transitioned my document project to iOS 18.4 from iOS 17.4, the DocumentGroup's closure runs twice both on device, and simulator. This means that if this closure runs say ContentView(document:), it does this twice in iOS 18.4 (probably 18.x). This project uses FileDocument I created a new document project from the document app template, and it exhibits the same double load behavior in iOS 18.4, and single load behavior in iOS 17.4. Both tests are run in the simulator. Does this behavior reflect a semantic requirement where the app should be able to work with multiple document loads, or is this a bug in the document system. Compiling with Swift 5 or Swift 6 for iOS 18.4. The template provided FileDocument adopted document is used with no changes. ...App.swift: import SwiftUI @main struct Double_Document_Start_ProblemApp: App { var body: some Scene { DocumentGroup(newDocument: Double_Document_Start_ProblemDocument()) { file in ContentView(document: file.$document) } } } =========================== ContentView.swift: import SwiftUI struct ContentView: View { static private var startCount: Int = 0 @Binding var document: Double_Document_Start_ProblemDocument var body: some View { Text(document.text) .onAppear { Self.startCount += 1 // GDEBUG print("Text start: \(Self.startCount).") } //TextEditor(text: $document.text) } } #if false #Preview { ContentView(document: .constant(Double_Document_Start_ProblemDocument())) } #endif =========================== Copy/paste of console output: Text start: 1. Text start: 2. ===========================