Search results for

LLDB crash

30,299 results found

Post

Replies

Boosts

Views

Activity

Reply to NSFileManager getRelationship:ofDirectoryAtURL:toItemAtURL:error: returning NSURLRelationshipSame for Different Directories
Thanks for the reply! I actually stumbled across this while reworking things in my app to account for NSURL caching behavior I mentioned in the other thread. What I was doing not too long ago was using an NSCache on top of NSURL for resource values. At some point when responding to metadata changes I was calling -removeCacheResourceValues on a background thread to get refreshed data and I had discovered that -removeCacheResources could crash if another thread was reading at the same time. I guess at some point in my frustration I just moved some stuff around to stop the crashes (and I did). I had either forgotten or just never realized that NSURL caches only for a run loop turn (or maybe just sometimes? More on that in a second). I guess this is cool in the middle of a dragging session but apparently at some point I must've just assumed that NSURL must be caching for a more meaningful period of time (from the perspective of my app anyway) because if I didn't call -removeCachedResources I'd g
Topic: App & System Services SubTopic: General Tags:
10h
iOS 26.3: Memory crash with @AppStorage and view transitions
I'm experiencing consistent memory crashes in iOS 26.3 (23D127) when using @AppStorage with view transitions. Environment: Device: iPhone 17 Pro Max iOS: 26.3 (23D127) Xcode: 26.2 (17C52) Issue: App crashes with Terminated due to memory issue when: Using @AppStorage to manage state Calling UserDefaults.set() in completion handler Transitioning to new view based on changed state Workaround: Using @State instead of @AppStorage prevents crash. Feedback: FB############ (your number) Has anyone else experienced this? Is this a known issue in iOS 26?
Topic: UI Frameworks SubTopic: SwiftUI
0
0
17
14h
Apple Watch: Restarts and overheating after watchOS 26.3 update
Hi there, I’ve been having ongoing issues with my Apple Watch. Last week I updated it to watchOS 26.3. The next day it accidentally ran out of battery, and since then it has been randomly restarting, showing an overheating message. I suspected it might be related to the update, so I researched online and on the official Apple forums. People recommended resetting the Apple Watch and unpairing it from my iPhone. I did both procedures, but the problem persists, even when the watch is in a cool environment. I’ve been using it normally, but it still restarts multiple times a day. Yesterday I even updated to the public beta of watchOS 26.4 hoping it would fix the issue, but it didn’t help — the random restarting continues. Today I also unpaired and paired it again with my iPhone, and the problem is still happening. This has been very disruptive and frustrating. I’m following up on my previous message because I’ve found additional diagnostic information that may help identify the cause of the issue. I accessed the A
Topic: App & System Services SubTopic: General Tags:
1
0
34
19h
Reply to Timed-Wait for main thread
[quote='816179021, GangOrca, /thread/816179, /profile/GangOrca'] Whereas, with conditional variables, there are no warnings. [/quote] I wouldn’t read too much into that. These warnings have to be explicitly coded, and we added that code for Dispatch semaphores because that’s the most common offender here. It wouldn’t surprise me if we added a similar warning for pthread condition variables at some point in the future. Then again, it wouldn’t surprise me if we didn’t. The pthreads API is relatively obscure. [quote='816179021, GangOrca, /thread/816179, /profile/GangOrca'] What is the recommend way? [/quote] There isn’t a supported way to block the main thread of a GUI application for long periods of time. On macOS it will SPOD, which is a terrible user experience. On other platforms the app will likely end up being killed by the watchdog. And to be clear, the issue here isn’t about the specific APIs you’re using, it’s this overall design. Speaking of iOS and friends, app termination [1] behaves very differently
Topic: App & System Services SubTopic: Core OS Tags:
23h
Reply to Xcode cloud
Thank you for your post. When Xcode crashes, it is advisable to file a bug report. Ensure that you are utilizing the latest version of Xcode. Updates to Xcode frequently incorporate bug fixes and enhancements to its integration with Xcode Cloud. Additionally, consider updating to the most recent stable release through the Mac App Store or the Developer Portal, as well as updating to the latest version of macOS. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
1d
Xcode cloud
I'm facing an issue with Xcode Cloud. Every branch I push to my GitLab repository is not appearing as selectable when I try to create a build with my workflow. Additionally, if I try to update the workflow from Xcode, it crashes every time I save the changes. Any help would be appreciated. Translated Report (Full Report Below) ------------------------------------- Process: Xcode [32110] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 26.2 (24553) Build Info: IDEApplication-24553000000000000~2 (17C52) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.apple.dt.Xcode [58945] User ID: 501 Date/Time: 2026-02-19 13:11:54.9987 -0600 Launch Time: 2026-02-19 13:03:37.7725 -0600 Hardware Model: Mac16,5 OS Version: macOS 26.2 (25C56) Release Type: User Crash Reporter Key: 61D7E2DA-E724-EFE2-6A01-25079BFCA2D1 Incident Identifier: B3D4A277-7CB5-4696-A00F-057929659F41 Sleep/Wake UUID: 2D4F6C41-716C-4B47-8D40-27FD2D74A8AE Time
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
1
0
40
1d
SwiftData + CloudKit: BGSystemTaskScheduler Code=8
Hi everyone, On macOS 26.4 beta (with Xcode 26.4 beta), I’m seeing the following console messages in a brand new SwiftData + CloudKit template project (no custom logic added, fresh CloudKit container): updateTaskRequest called for a pre-running task com.apple.coredata.cloudkit.activity.export.F9EE783D-7521-4EC2-B42C-9FD1F29BA5C4 updateTaskRequest called for an already running/updated task com.apple.coredata.cloudkit.activity.export.F9EE783D-7521-4EC2-B42C-9FD1F29BA5C4 Error updating background task request: Error Domain=BGSystemTaskSchedulerErrorDomain Code=8 (null) These messages appear: When CloudKit is enabled Occasionally on app launch Often when bringing the app back to the foreground (Cmd-Tab away and back) Even with zero additional SwiftData logic They do not appear when CloudKit is disabled. This behavior is reproducible on a completely new project with a fresh CloudKit container. Questions: What exactly do these messages indicate? Is BGSystemTaskScheduler Code=8 expected in this context? Are these sa
Topic: App & System Services SubTopic: iCloud & Data Tags:
2
0
47
1d
Reply to What should be enabled for Enhanced Security?
[quote='876600022, anosidium, /thread/815819?answerId=876600022#876600022, /profile/anosidium'] You advised that I should enable all the settings. [/quote] Well, yes, if you read that one sentence in isolation. However, I made it clear that one specific setting, Enable Soft Mode for Memory Tagging, reduces security, so if you goal is security then enabling that is probably not a good choice (-: [quote='876600022, anosidium, /thread/815819?answerId=876600022#876600022, /profile/anosidium'] I am therefore inclined not to enable it. [/quote] Or you could profile your app and see if it makes a difference in pratice. That’s generally the best way to approach performance trade-offs. [quote='876600022, anosidium, /thread/815819?answerId=876600022#876600022, /profile/anosidium'] I am not entirely sure what is meant by logging in [Soft Mode] [/quote] Quoting Enabling enhanced security for your app: This entitlement makes hardware memory tagging operate in soft mode, where the system produces a simulated crash
Topic: Privacy & Security SubTopic: General Tags:
1d
Reply to vImageBuffer_InitWithCGImage fails with Xcode 26 but succeeds with Xcode 15I am
Thank you for doing some testing. That is great. I am a little confused though. I uploaded the image file earlier on the thread. I have reuploaded for this reply. Its name is PXL_20251217_201630453.MP.jpeg . Note also that the sample code contained the line: format.bitmapInfo = kCGImageAlphaFirst | kCGBitmapByteOrderDefault;//ARGB8888 That is slightly different than what you tried. Note also that my code did not crash. vImageBuffer_InitWithCGImage returned with the error code kvImageInvalidParameter. A complete project to reproduce the error has been uploaded as a zip archive via Feedback Assistant. Feedback Assistant designates the report as FB21893783 . The jpeg file is also in the zip archive. Xcode debug console: -[MoeDocController openDocumentWithContentsOfURL:display:completionHandler:] file:///Users/elliotleonard/test/PXL_20251217_201630453.MP.jpeg fence tx observer 1f8eb timed out after 0.600000 <<<< CMPhotoJFIFUtilities >>>> signalled err=-17102 at <>:1776 <&
Topic: Graphics & Games SubTopic: General Tags:
2d
Reply to vImageBuffer_InitWithCGImage fails with Xcode 26 but succeeds with Xcode 15I am
Hello. I tested using Xcode Version 26.2 (17C52) on macOS 26.2 (25C56) using your code with the following color format files and I was unable to reproduce a crash. Can you provide a copy of the image file you are using for testing? Formats I tried: RGB_NoneSkipFirst_8bit 8 bits/component, 32 bits/pixel RGBX format (no alpha, skip first byte) sRGB color space AlphaInfo: kCGImageAlphaNoneSkipFirst RGB_NoneSkipLast_8bit 8 bits/component, 32 bits/pixel XRGB format (no alpha, skip last byte) sRGB color space AlphaInfo: kCGImageAlphaNoneSkipLast RGB_AlphaPremultFirst_8bit 8 bits/component, 32 bits/pixel ARGB format with premultiplied alpha sRGB color space AlphaInfo: kCGImageAlphaPremultipliedFirst RGB_AlphaPremultLast_8bit 8 bits/component, 32 bits/pixel RGBA format with premultiplied alpha sRGB color space AlphaInfo: kCGImageAlphaPremultipliedLast RGB_AlphaPremultLast_16bit 16 bits/component, 64 bits/pixel RGBA format with premultiplied alpha sRGB color space AlphaInfo: kCGImageAlphaPremultipliedLast RGB
Topic: Graphics & Games SubTopic: General Tags:
2d
Reply to When AI leads to lost prompts (26.3)
The Xcode team is here! Thanks for reporting this, I'm seeing the lost prompt as well when starting a new conversation. The crash sounds quite unfortunate and is not something I've seen. A bug report would be great, especially if you have reproducible steps or a screen recording. Even the crash report would be very informative. Thank you for reporting!
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2d
Reply to Is calling different SBApplication objects from different threads bad?
That's a no-go. Jobs just have to run until they are done. There are dozens, if not hundreds, of pieces of data that are built and used along the way. Some of them are hogs that will run for 3 hours. Long running is a very relative concept, as there's a huge difference between 3 hours” -> “3 days” -> “3 months. Strictly speaking, it's not even REALLY about time itself, at least not on its own. There are basically a few different goals I'd be looking at here: Isolating your work activities from each other so that they can't interfere with each other. Reducing the complexity of the long running component such that it's easier to test/validate/etc. Reducing the execution timeline to something that can reasonably be tested (“week” vs “month”). The first goal basically solves the immediate crash you're looking at. That is, it's fairly clear that the crash involves some kind of interaction between multiple SBApplication threads, so it can't happen when there's only one thread. Moving to the
Topic: App & System Services SubTopic: Automation & Scripting Tags:
2d
Reply to Is calling different SBApplication objects from different threads bad?
or the SB/AE world that fails So, in the process of writing up the message that follows this one, I actually had a breakthrough about what might be involved in triggering this crash. That is, I don't think it's necessarily CAUSING the crash, but I think it is part of the situation that creates the crash. Here is the crashing thread on all three crashes you sent: 0 com.apple.AE 0x1a7d970cc isMachReplyOutstanding(short) + 92 1 com.apple.AE 0x1a7d89b80 absolveReturnID(short) + 92 2 com.apple.AE 0x1a7d8994c AEEventImpl::AEEventImpl(unsigned int, unsigned int, AEDesc const*, short, int) + 100 3 com.apple.AE 0x1a7d85bfc AECreateAppleEvent + 416 What absolveReturnID actually does is generate the random 16-bit ID used when using kAutoGenerateReturnID, which is then checked as unused by calling isMachReplyOutstanding. However, the interesting detail here is that absolveReturnID also has a fixed cache of the last (~64) IDs, so it can just skip those IDs instead of checking f
Topic: App & System Services SubTopic: Automation & Scripting Tags:
2d
Reply to What should be enabled for Enhanced Security?
Thanks @DTS Engineer, I have already read that documentation. You advised that I should enable all the settings. However, I noticed that for Memory Tag Pure Data, the description states that “it may incur a performance overhead”. I am therefore inclined not to enable it. Regarding Enable Soft Mode for Memory Tagging, the description states that “memory tagging faults will not crash and will be logged instead”. I am inclined to leave this disabled, as I would prefer the application to crash so that I can receive a crash report and potentially fix the issue. I am not entirely sure what is meant by logging in this context, would this appear in the Xcode console when running in Debug mode? As you are knowledgeable about AppKit and Mac computers, may I ask if you would mind looking at my other post about StoreKit 2? I am at my wits’ end, as I would like to ship the Cocoa app using the API but cannot because it is not behaving as expected. I am tempted to submit a code-level support reque
Topic: Privacy & Security SubTopic: General Tags:
2d
Reply to EXC_BAD_ACCESS issue need advice
[Different DTS engineer here; I’m picking up this thread because it’s directly aligned with my area of expertise.] [quote='876554022, Tenjikato, /thread/815899?answerId=876554022#876554022, /profile/Tenjikato'] it does not appear in Xcode Organizer. [/quote] Right. The issue here is that you have a third-party crash reporter installed and it’s failing to preserve the Apple crash report. Let’s look at the backtrace in your first post: Crashed: com.apple.main-thread 0 KSCrash … ksmemory_notifyUnhandledFatalSignal + 12 1 KSCrash … handleSignal + 100 2 libsystem_platform.dylib … _sigtramp + 56 3 libsystem_kernel.dylib … mach_msg2_internal + 76 4 libsystem_kernel.dylib … mach_msg_overwrite + 428 5 libsystem_kernel.dylib … mach_msg + 24 6 CoreFoundation … __CFRunLoopServiceMachPort + 160 7 CoreFoundation … __CFRunLoopRun + 1188 8 CoreFoundation … _CFRunLoopRunSpecificWithOptions + 532 9 GraphicsServices … GSEventRunModal + 120 10 UIKitCore … -[UIApplication _run] + 792 Frames 10 through 3
Topic: Developer Tools & Services SubTopic: General Tags:
3d