Search results for

LLDB crash

29,555 results found

Post

Replies

Boosts

Views

Activity

Reply to "Assertion failed: (false) function _onqueue_rdar53306264_addWaiter file TubeManager.cpp line 1042" Crash
Right. The second file is from a third-party crash reporter, which is rarely helpful [1]. The second is from the Apple crash reporter, but it’s in human readable format (.crash). I’m looking for a crash report in the JSON format (.ips). Do you have one of those? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] For an explanation of why third-party crash reporters are a bad idea, see Implementing Your Own Crash Reporter.
Topic: App & System Services SubTopic: Networking Tags:
Aug ’25
Reply to Wi-Fi Aware Sample APP crashes on iOS 26 beta 6
If our sample code is crashing out of the box, it’s always worth filing a bug about that. It’s gotta be either a problem with the sample or a problem with the OS, or maybe a problem with Xcode. Regardless, it’s our issues to fix. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Networking Tags:
Aug ’25
Reply to For the property modifiers of XIB controls, should we use strong or weak?
A crash report is a point-in-time capture of the call stack leading up to the crash. While useful as a starting point to making are you understand the call path that got you to the crash, it doesn't contain the information about how your views were either strongly or weakly referenced in memory, and how those references changed over the lifetime of your view, which then lead to the view being released unexpectedly. You'll need to do further debugging of your code to understand the references you have, according to the rules of strong and weak references and the information I wrote above. The Allocations instrument in Instruments is one tool that is helpful, and the Memory Graph debugger with MallocStackLogging enabled is another useful tool for debugging these types of issues. 24 UIKitCore 0x000000018e76f1cc -[UINib instantiateWithOwner:options:] + [ : 768] 25 UIKitCore 0x000000018e5eda0c -[UICollectionView _dequeueReusableViewOfKind:withIdentifier:forIndexPath:viewCategory:] + [ :
Topic: UI Frameworks SubTopic: UIKit Tags:
Aug ’25
Reply to Crash when assigning NSImage to `@objc dynamic var` property
they actually CREATE crashes Thanks, that's what I should have known but didn't fully realize until now. I just tried enabling the Address and Thread Sanitizer (the Main Thread Checker is already enabled), but couldn't reproduce the crash. I'll keep them enabled in the hope that they will create a crash at some point. whatever is going on doesn't involve some simple code flow I could understand that this crash could be caused by multiple threads releasing the image at the same time, but if only the main thread is accessing them, I cannot imagine how they could be over-released. I'm not doing any manual memory management with them or their parent object. If you have any example of how over-releasing could happen without thread contention and manual memory management, I'd be eager to hear it. Otherwise I'll let you know as soon as I'm able to reproduce the crash.
Topic: UI Frameworks SubTopic: AppKit Tags:
Aug ’25
Reply to Crash when assigning NSImage to `@objc dynamic var` property
I don't understand. Aren't all these tools you mention (Zombies instrument, ASan, Main Thread Checker etc.) meant to be run in Xcode or Instruments? Or are you saying I should enable some compiler flag in my production build? They're intended to run in your development build. Let me jump back to what you're saying here: since the crash reports are downloaded by Xcode from other users and I cannot reproduce it myself... What you're saying here is testing in Xcode won't help because I can't reproduce the issue. The problem with that statement is that it misunderstands how the tools above actually work. They don't just provide better diagnostic data about a crash that would otherwise occur, they actually CREATE crashes that would otherwise NOT occur. Jumping back to my description here: However, what the Zombies instrument actually does is modify the dealloc method so that freeing an object doesn't ACTUALLY free that object, but instead replaces it with an intentionally invalid object
Topic: UI Frameworks SubTopic: AppKit Tags:
Aug ’25
AVPlayerViewController `customInfoViewControllers` crash/workaround on tvOS 26
One thing I've noticed on tvOS 26 is that if you try to set the AVPlayerViewController customInfoViewControllers property while the Content Tabs are on screen, your app will crash. *** Terminating app due to uncaught exception 'UIViewControllerHierarchyInconsistency', reason: 'trying to add child view controller that is already presented: ' *** First throw call stack: (0x18a7167bc 0x189a77510 0x18a7166a8 0x1ab425658 0x1b2ee9d54 0x1b2efcd60 0x1b2eaf3f0 0x1080f744c 0x107e021a8 0x107e01b3c 0x18de41c14 0x18de41ba8 0x18de48d28 0x18ad9e358 0x101fac5f0 0x101fc6228 0x101fe7278 0x101fbc6fc 0x101fbc63c 0x18a67a2e0 0x18a679418 0x18a673b34 0x1937e4d5c 0x1abb36588 0x1abb3ae80 0x1aae9dec4 0x108610174 0x1086100e4 0x108615140 0x189abd4d0) I've logged a feedback (FB19554461) but it's getting awfully late in the dev cycle. So I've been trying to think of a workaround. The problem is that customInfoViewControllers is pretty declarative in nature. There are no properties or delegate methods I am aware of that let me kno
Topic: Media Technologies SubTopic: Video Tags:
1
0
90
Aug ’25
Reply to Xcode Beta (Version 26.0 beta 5 (17A5295f)) Constantly Crashing!
it works for me (M1 MBA and M1 MBP with M1 Pro). If I were you, I'd file a bug, then delete Xcode 26b5 and everything associated with it, then re-install it. If that doesn't work, and you're on a beta of macOS, wipe the Mac and reinstall everything. If it is still a problem, follow up on the bug with new crash logs. If it is fixed, close the bug with cannot reproduce.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Aug ’25
iOS 26 crashes with CALayerInvalidGeometry when using magnifier on Webview
I have a Net8 Maui WebView app and whenever I use magnifier, it crashes. The magnifier works on iOS18 and lower but crashes on iOS26+ Exception **Type:** CALayerInvalidGeometry **Value:** CALayer position contains NaN: [nan 65]. Layer: >; sublayers = (, ); opaque = YES; allowsGroupOpacity = YES; anchorPoint = CGPoint (inf 0); opacity = 0> Stacktrace __exceptionPreprocess in unknown file [Line null, column null] (Not in app) objc_exception_throw in unknown file [Line null, column null] (Not in app) +[NSException raise:format:] in unknown file [Line null, column null] (Not in app) CA::Layer::set_position in unknown file [Line null, column null] (Not in app) -[CALayer setPosition:] in unknown file [Line null, column null] (Not in app) -[UIView _backing_setPosition:] in unknown file [Line null, column null] (Not in app) -[UIView setCenter:] in unknown file [Line null, column null] (Not in app) -[_UIEditMenuContentPresentation _displayPreparedMenu:titleView:reason:didDismissMenu:configurati
Topic: Safari & Web SubTopic: General
2
0
194
Aug ’25
macOS 26: NSTokenField crashes due to NSGenericException caused by too many Update Constraints
This example application crashes when entering any text to the token field with FAULT: NSGenericException: The window has been marked as needing another Update Constraints in Window pass, but it has already had more Update Constraints in Window passes than there are views in the window. The app uses controlTextDidChange to update a live preview where it accesses the objectValue of the token field. If one character is entered, it also looks like the NSTokenFieldDelegate methods tokenField(_:styleForRepresentedObject:) tokenField(_:editingStringForRepresentedObject:) tokenField(_:representedObjectForEditing:) are called more than 10000 times until the example app crashes on macOS Tahoe 26 beta 6. I've reported this issue with beta 1 as FB18088608, but haven't heard back so far. I have multiple occurrences of this issue in my app, which is working fine on previous versions of macOS. I haven't found a workaround yet, and I’m getting anxious of this issue persisting into the official release.
Topic: UI Frameworks SubTopic: AppKit Tags:
0
0
62
Aug ’25
Reply to @State variable returns empty despite being set in .onAppear function
Another point. In DataView, index should not be a State variable. Add a button in ContentView VStack { if showView && (index >= 0) && (index < data.count) { DataView(datum: data[index]) } Spacer() HStack { Text(Index: (index) -> ) Button(Next) { index += 1 if index >= data.count { index = 0 } } } } You will see that text in DataView does not change Text(DataView (datum.str)) always says DataView String 1 Now change DataView as follows to get it updated on index change by button press: struct DataView: View { /*@State*/ var datum: Data2 var body: some View { Text(DataView (datum.str)) } } Note: I renamed data to datum for an array item, to differentiate from the array. Now, I have to update my initial answer. In fact, no need for showView and Dispatch (even though that made it work). Just test index: if (index < data.count) { DataView(datum: data[index]) Without the index test, it crashes… Swift/ContiguousArrayBuffer.swift:691: Fatal error: Index out of range Reason is t
Topic: Design SubTopic: General Tags:
Aug ’25
Reply to "Assertion failed: (false) function _onqueue_rdar53306264_addWaiter file TubeManager.cpp line 1042" Crash
We are glad to receive your reply. The crashes we encountered indeed occurred on iOS 16. Here is the crash report we have collected. 2025-08-11_08-00-36.7327_+0100-8e5932e50fad855083676ed1d14993f8028995a9.crash live.soulchill.ios_issue_978f48b6bc841ec59315428834ff62f3_crash_session_c4ff2e4f47d74f1a84b3b40404880b83_DNE_0_v2_stacktrace.crash
Topic: App & System Services SubTopic: Networking Tags:
Aug ’25
Reply to Dynamic Library cannot call exposed C function
Thanks for the crash report. The standard DTS mantra is “Always ask for a crash report first.” I failed to do that in this case, to my own detriment )-: The crash report snippet in your original post, and the discussion of Rust and so on, confused me into thinking that this problem is more complex than it is. However, your crash report makes it clear as to exactly what’s going on: Thread 3 name: Thread 3 Crashed: 0 ??? 0x0000000000000000 0x0 + 0 1 sdk 0x0000000105931ec0 0x105820000 + 1121984 This isn’t a weird code signing issue. Rather, your code has simply jumped to nil. [quote='853477022, ospfranco, /thread/795348?answerId=853477022#853477022, /profile/ospfranco'] I guess cocoapods masqueraded the issue. [/quote] Possibly. I often see cross-platform code deploy the -undefined linker option, which has a tendency to turn build-time errors into run-time errors. Needless to say, I’m not a fan [1]. If you’re curious about how Mach-O symbols work, I talk about that ex
Topic: Code Signing SubTopic: General Tags:
Aug ’25
Reply to "Assertion failed: (false) function _onqueue_rdar53306264_addWaiter file TubeManager.cpp line 1042" Crash
For those reading along at home, zhenYang sent me full copies of their crash reports via a different channel. Which is why I haven’t asked for them here (-: [quote='796647021, zhenYang, /thread/796647, /profile/zhenYang'] mainly occurring on iOS 16 systems [/quote] Mainly? Or exclusively? What’s the most modern OS release where you’ve seen this crash? Also, are you able to get a JSON format crash report (.ips) for this issue? If so, please post it here. That opens up more avenues for me to investigate this internally. See Posting a Crash Report for advice on how to post crash reports. ps The Radar bug indicated by that symbol name (r. 53306264) was resolved in iOS 13, so it’s unlikely to be a concern here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Networking Tags:
Aug ’25