Search results for

LLDB crash

29,557 results found

Post

Replies

Boosts

Views

Activity

Reply to Crash when assigning NSImage to `@objc dynamic var` property
The code is called on the main thread. According to the crash report, thread 0 makes that assignment, Looking at the crash log, the abort originates here: 4 libobjc.A.dylib 0x00000001818d7fc0 _objc_fatal(char const*, ...) + 44 (objc-errors.mm:232) 5 libobjc.A.dylib 0x00000001818a6d78 weak_register_no_lock + 396 (objc-weak.mm:423) 6 libobjc.A.dylib 0x00000001818a6b40 objc_storeWeak + 472 (NSObject.mm:408) As it happen, you don't have to guess at why weak_register_no_lock failed, as the project is opensource. Here is the line that's crashing: _objc_fatal(Cannot form weak reference to instance (%p) of class %s. It is possible that this object was over-released, or is in the process of deallocation., (void*)referent, object_getClassName((id)referent)); That leads to here: and at the same time thread 16 is calling [NSImageView asynchronousPreparation:prepareResultUsingParameters:]. Unfortunately, I wouldn't necessarily assume this call is directly involved. From the large context in th
Topic: UI Frameworks SubTopic: AppKit Tags:
Aug ’25
libiconv crashes on iOS 18, iOS 16 beta and macOS 15 for certain combinations of strings and encodings
When converting a string using libiconv, for certain combinations of strings and encodings, sometimes iconv() crashes Assertion failed: (tmpin - *in <= *inbytes), function _citrus_iconv_std_iconv_convert, file citrus_iconv_std.c, line 1916. This means that libiconv is a debug build since it asserts and also that it doesn't handles certain characters, it should not crash but return some error code. I've reported this problem twice to Apple, nothing happens. FB17715360 and FB17567155 Below is a simple code snippet that illustrates the problem: #include <iconv.h> #import <Foundation/Foundation.h> void TestLibIconv() { NSLog(@Convert a string from some encoding to some other); NSLog(@The in string may have some unknown encoding); const char *inEnc = SHIFT_JIS; // Japanese //const char *inEnc = CP1252; // works const char *outEnc = UTF-8; NSLog(@inEnc %s outEnc %s, inEnc, outEnc); iconv_t cd = iconv_open(outEnc, inEnc); if (cd != (iconv_t) -1) { #if 1 // works when this flag isn't
2
0
143
Aug ’25
Reply to Crash in Swift 6 when using UNUserNotification
@Engineer Thanks for reply. Some more crash info. On simulator (did not test on device at this stage). Here is crash report: Error occurs in #4 notifyMe IBAction @IBAction func notifyMe(_ sender: UIButton) { let center = UNUserNotificationCenter.current() center.delegate = self center.getNotificationSettings(completionHandler: { (settings) in if settings.authorizationStatus == .notDetermined { center.requestAuthorization(options: [.alert, .sound, .badge]) { (granted, error) in DispatchQueue.main.async { if !granted { // Alert user } } } } else if settings.authorizationStatus == .denied { DispatchQueue.main.async { // Alert user } } else if settings.authorizationStatus == .authorized { DispatchQueue.main.async { self.alarmButton.isHidden = self.duree <= 120 } } }) var alertStyle = UIAlertController.Style.alert let alertController = UIAlertController( title: NSLocalizedString(M'avertir, comment: ), message: NSLocalizedString(Attention, comment: ), preferredStyle: alertStyle) var title = NSL
Aug ’25
Xcode always crash.
OS version:15.6 (24G84). mac mini m 4 Xcode:16.4 stack: Translated Report (Full Report Below) Process: Xcode [5261] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 16.4 (23792) Build Info: IDEApplication-23792000000000000~2 (16F6) App Item ID: 497799835 App External ID: 874973124 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-08-11 19:57:18.7642 +0800 OS Version: macOS 15.6 (24G84) Report Version: 12 Anonymous UUID: 314F3813-7BB3-0263-1826-79D64A62D963 Time Awake Since Boot: 700 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x00000001ab5dc1f8 Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5 Terminating Process: exc handler [5261] Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libswiftCore.dylib 0x1ab5dc1f8 assertionFailure(:_:file:line:flags:) + 176 1 libsw
2
0
73
Aug ’25
Reply to macOS26: MenuBarExtra item not showing
Hi, Indeed, I do not see any call to NSApplicationMain just like you have: Thread 0 Crashed: 0 libsystem_kernel.dylib 0x19f8e85b0 __pthread_kill + 8 1 libsystem_pthread.dylib 0x19f922848 pthread_kill + 296 2 libsystem_c.dylib 0x19f828808 abort + 124 3 kDrive 0x1009954a4 KDC::AppServer::init()::$_1::operator()() const + 20 (appserver.cpp:404) 4 kDrive 0x100995450 QtPrivate::FunctorCall<>, QtPrivate::List<>, void, KDC::AppServer::init()::$_1>::call(KDC::AppServer::init()::$_1&, void**) + 44 (qobjectdefs_impl.h:146) 5 kDrive 0x1009953ec void QtPrivate::Functor::call<>, void>(KDC::AppServer::init()::$_1&, void*, void**) + 36 (qobjectdefs_impl.h:256) 6 kDrive 0x100995388 QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) + 168 (qobjectdefs_impl.h:420) 7 QtCore 0x10520b0d8 QtPrivate::QSlotObjectBase::call(QObject*, void**) + 20 (qobjectdefs_impl.h:375) [inlined] 8 QtCore 0x10520b0d8 QSingleShotTimer::timerEvent(QTimerEven
Aug ’25
iOS26 wkWebview Crash CALayer position contains NaN
On my native app, will open a wkWebview to display some content. And it will crash on iOS26: *** Terminating app due to uncaught exception 'CALayerInvalidGeometry', reason: 'CALayer position contains NaN: [nan 103.667]. Layer: >; sublayers = (, ); opaque = YES; allowsGroupOpacity = YES; anchorPoint = CGPoint (inf 0); opacity = 0>'
Topic: Safari & Web SubTopic: General Tags:
3
0
350
Aug ’25
Crash in Swift 6 when using UNUserNotification
After porting code to Swift 6 (Xcode 16.4), I get a consistent crash (on simulator) when using UNUserNotificationServiceConnection It seems (searching on the web) that others have met the same issue. Is it a known Swift6 bug ? Or am I misusing UNUserNotification ? I do not have the crash when compiling on Xcode 26 ß5, which hints at an issue in Xcode 16.4. Crash log: Thread 10 Queue : com.apple.usernotifications.UNUserNotificationServiceConnection.call-out (serial) As far as I can tell, it seems error is when calling nonisolated func userNotificationCenter(_ center: UNUserNotificationCenter, willPresent notification: UNNotification, withCompletionHandler completionHandler: @escaping (UNNotificationPresentationOptions) -> Void) I had to declare non isolated to solve a compiler error. Main actor-isolated instance method 'userNotificationCenter(_:didReceive:withCompletionHandler:)' cannot be used to satisfy nonisolated requirement from protocol 'UNUserNotificationCenterDelegate' I w
4
0
125
Aug ’25
Why doesn’t Apple fix Xcode’s performance and stability issues?
**Background: Many iOS/macOS developers have faced issues like: • Autocomplete randomly stopping • Indexing freezing or slowing down • SwiftUI previews breaking unexpectedly • Build process hanging or crashing Even after multiple updates, these issues seem to come back in different forms. ** Do you think Apple should consider a full architectural rewrite of Xcode? Would separating SDK updates from IDE updates help? How do you personally deal with Xcode’s instability in your workflow?
1
0
126
Aug ’25
Crash on Launch – iPad Air (5th Gen) – iPadOS 18.6 – Address Size Fault (Case-ID: 15374981)
We are dealing with a launch-time crash that happens every time in Apple’s review environment, but does not occur in any of our local or TestFlight testing. Case-ID: 15374981 Device in Review: iPad Air (5th generation) OS in Review: iPadOS 18.6 Build Environment: Xcode 15.x → Archive → Export for App Store Connect Deployment Target: iOS 14.0+ Architecture: arm64 What Happens In Apple’s review environment: app launches → no UI → immediate crash. We have 8 crash logs from App Review — all with identical stack signatures. In our testing: the same build runs without issue on: iPad Air (5th gen) – iPadOS 18.5, 18.6 iPad Pro 11 – iPadOS 18.5, 18.6 Multiple iPhone models – iOS 17.x / 18.x Crash Log Signature (main thread) Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS Termination Reason: Address size fault Crashed Thread: com.apple.main-thread 0 libsystem_kernel.dylib mach_msg2_trap + 8 1 libsystem_kernel.dylib mach_msg_overwrite + 428 2
0
0
113
Aug ’25
Reply to Insight into BaseBoard/FrontBoardServices Crashes Needed
Here's the crash report, as downloaded using Xcode's organizer. Will this work? I redacted the app and framework names. All of our symbols are symbolicated, except for MyFramework, which is a C++ library of ours whose only job is to decode video, so I think it's irrelevant to this crash. 2025-07-28_00-11-07.8114_-0600-ddc7ad494d0b81224d315ee28d9b96d7aca9a9ca.crash I'll take another look at that tech note. I've gone over it before, but maybe I'll find something if I look again. Thank you!
Topic: UI Frameworks SubTopic: General Tags:
Aug ’25
Reply to Initializing LanguageModelSession crashes app on macOS
Thank you @DTS Engineer! This was exactly what I had, I was building with Xcode Beta 5 and running on previous iOS 26 versions. Because of the symbol changes, building with Xcode 26 Beta 5 and running on macOS / iOS 26 Beta 4 / 3 may trigger the crash. I was able to run properly after upgrading my iOS device to Beta 5 and no more crashes! It seems you'll need to be on both Xcode 26 Beta 5 + iOS 26 Beta 5.
Aug ’25