Search results for

“LLDB crash”

30,536 results found

Post

Replies

Boosts

Views

Activity

WKWebView + Bluetooth Keyboard: Ctrl+Home / Ctrl+End causes app crash after input blur (iPadOS 18.4.1 / 18.6.2)
1. Summary In a hybrid iOS app using WKWebView (Angular + Capacitor), after programmatically blurring an element and connecting a Bluetooth keyboard, pressing Ctrl+Home or Ctrl+End causes the app to crash. The crash stack shows the issue occurs inside UIKit keyboard handling (UITextInteractionSelectableInputDelegate _moveToStartOfLine), indicating a system-level bug. 2. Steps to Reproduce Open the hybrid app containing a WKWebView. Blur the input (programmatically). Connect a Bluetooth keyboard. Press Ctrl + Home or Ctrl + End. Expected result: No crash. The command should be ignored if no text input is active. Actual result: App crashes immediately. 3. Crash Log (Crashlytics Trace) Crashed: com.apple.main-thread 0 WebKit 0xfbdad0 + 236 1 UIKitCore 0x10b0548 -[UITextInteractionSelectableInputDelegate _moveToStartOfLine:withHistory:] + 96 2 UIKitCore 0xd0fb38 -[UIKBInputDelegateManager _moveToStartOfLine:withHistory:] + 188 3 UIKitCore 0xa16174 __158-[_UIK
1
0
193
Feb ’26
LLDB assertion failure when debugging Swift app
While debugging a Swift application in Xcode, LLDB crashes with an assertion failure related to LLDBMemoryReader and pointer authentication. The issue occurs during normal debugging (e.g. inspecting variables or stack frames), and causes the debugger to become unusable. The error appears to be triggered inside the Swift language runtime reflection path in LLDB error: Assertion failed: (LLDBMemoryReader module to address map ran into pointer authentication mask!), function addModuleToAddressMap, file /AppleInternal/Library/BuildRoots/603ae698-b099-11ef-b64c-aabfac210453/Library/Caches/com.apple.xbs/Sources/lldb/llvm-project/lldb/source/Plugins/LanguageRuntime/Swift/LLDBMemoryReader.cpp, line 537 Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it): 0 LLDB 0x00000001240eb8f8 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 40 1 LLDB 0x0000000123bbd0a8 lldb_pri
1
0
124
Feb ’26
Reply to Bug? SwiftData + inheritance + optional many-to-one relationship
I encountered another bug with SwiftData and inheritance and reported it (FB21837287). This one is not related to CloudKit. Briefly, SwiftData crashes during auto-save when the schema contains: A base @Model class with at least one subclass (inheritance) A separate @Model class with a reference to the base class The crash occurs specifically when: There is a class inheritance hierarchy (Beta: Alpha) A separate class (Standalone) has a reference typed as the base class (Alpha?) Changing the reference from var ref: Alpha? to var ref: Beta? (subclass) eliminates the crash.
Feb ’26
symbolicate crashlog using .symbols files instead of dSYMs
Hi, Some crashes downloaded from TestFlight aren't symbolicated by Xcode and I don't know why, here's an example: Although all uploaded builds contain debug symbols (Symbols directory with .symbols files) and other crashlogs in the same version are symbolicated just fine (also visible on the above SS). I have access only to the .symbols files but not to the original dSYMs and I wonder how to perform symbolication manually. I tried pointing atos and symbolicatecrash utilities to respective .symbols file, but they are unable to work with it. I'm sure it's possible as TestFlight symbolicates crashlogs using only .symbols files somehow. Could you give a hint?
3
0
255
Feb ’26
Reply to M4 iPadOS stuck at Apple Logo on reboot.
I had the same problem with my M2 iPad Air, and ChatGPT told me to do this instantly worked. but you have to follow the instructions Yes — here’s the clean, repeatable fix for an iPad stuck in a reboot loop (Apple logo → restarts → logo again). Start at Step 1 and only move on if it doesn’t work. ⸻ Step 1 — Force restart (fastest, safest) This fixes temporary system crashes. If your iPad has Face ID (no Home button): 1. Quickly press Volume Up → release 2. Quickly press Volume Down → release 3. Press and HOLD Power 4. Keep holding until you see the Apple logo, then let go If your iPad has a Home button: 1. Hold Home + Power together 2. Keep holding until the Apple logo appears 👉 If it boots normally, you’re done. ⸻ Step 2 — Recovery Mode (most common real fix) Use this if it keeps looping. What you need • A Mac or Windows PC • A cable • Finder (Mac) or iTunes (Windows / older macOS) Steps 1. Connect iPad to the computer 2. Force-restart but DO NOT release when the Apple logo appears 3. Keep holding
Jan ’26
Reply to NSTextLineFragment crash - how to debug
Thanks for providing the reproducible case, which will greatly help the TextKit folks to address the issue from the framework side. As the reproducible case shows, the crash is triggered by a specific combination of attributes. Unless you can identify the cases and avoid them, I unfortunately don't see anything from the app side that can fix / work around the issue. I have added my comment to the feedback report (FB16905066). Thank you all again for making the feedback much more actionable by providing the project that reproduces the crash. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: UIKit Tags:
Jan ’26
Reply to Inserting an NSView (Cocoa) in NSWindowController Views hierarchy
For your first approach, are you able to provide information about the crash, like a crash log? For your second approach, it is common to see initial view hierarchy setup for a window in your window controller subclass’s overridden windowDidLoad method. For a view that just needs to display a solid color, NSBox can be used for this purpose: let box = NSBox() box.boxType = .custom box.borderWidth = 0.0 box.fillColor = NSColor.systemRed
Topic: UI Frameworks SubTopic: AppKit Tags:
Jan ’26
Reply to Horrible weird Window Server killing bug
This got even weirder. One is that sometimes the use of cos() would cause a compiler error, which was fixed by using Darwin.cos(). This may be fixed in Swift 6.3. The other thing is that in my much more complex code, the crash seemed to be caused by both the cos() call evaluating to 0, but only when the line being drawn with that result had a StrokeStyle applied to it. In anycase, I have filed Feedbacks explaining this, and I'm told the WindowServer team has had it brought to their attention.
Topic: UI Frameworks SubTopic: SwiftUI
Jan ’26
Inserting an NSView (Cocoa) in NSWindowController Views hierarchy
I have an NSWindowController with several IBOutlets created in storyboard. I want to add an NSView and fill it with some color. I need to place it at a specific position in views hierarchy. I have tried 2 ways, no one succeeds. First. include a custom view in storyboard connect to an IBOutlet in an init of controller, set the layer for the view Result: crash Second build programmatically Result: I do not find where to put this code in the controller code That's basic Cocoa, but way more painful than iOS.
Topic: UI Frameworks SubTopic: AppKit Tags:
3
0
379
Jan ’26
TUINSRemoteViewController over-release crash in ViewBridge during autorelease pool drain
Summary A crash occurs in ViewBridge framework when a TUINSRemoteViewController object receives -release message after being deallocated. This appears to be a reference counting issue within the ViewBridge framework's internal autorelease pool management. Environment macOS Version: [15.0.0] Application: Custom Qt-based application using Chromium Embedded Framework (xcode version: xcode 15; QT version: 6.5.4 ; CEF version: 138.0.47+g2728d53+chromium-138.0.7204.221) Steps to Reproduce Users are typically using the app normally, but a crash occasionally occurs when they activate and click on the application. This happens infrequently, but it occurs roughly every day. Currently, only a few specific users experience this crash, and it may appear for several consecutive days before disappearing for several days. We cannot reliably reproduce this issue but have collected crash logs from affected users. Crash Analysis Zombie Detection Log: Zombie received -release Dealloc
1
0
231
Jan ’26
Where did I screw up trying concurrency?
I tried making a concurrency-safe data queue. It was going well, until memory check tests crashed. It's part of an unadvertised git project. Its location is: https://github.com/CTMacUser/SynchronizedQueue/commit/84a476e8f719506cbd4cc6ef513313e4e489cae3 It's the blocked-off method `memorySafetyReferenceTypes' in SynchronizedQueueTests.swift. Note that the file and its tests were originally AI slop.
2
0
272
Jan ’26
Reply to why mapkit js does not have LookAroundSceneRequest
Ed Ford,  DTS Engineer Your reply does not help. I have look at the sample code thousands times before I ask this question here. The sample code, and document api does not mention how to update coordinate for the look around object. I need constantly change the look around scene coordinate, the sample code only create look around object based on one coordinate. If I need to update coordinate to a different location for this look around object, can you share the sample code to do this job here for everyone that is interested? This is my code, it destroy everytime before create a new one. It works, but it can crash browser webGL if user change coordinate 16 times and above , then it cause apple base map blank. ` // // --- --- apple look around --- // var lookAround var is_lookAround_load_complete = false var is_first_time_lookAround = true // only for 1st time load function create_apple_look_around(lookAround_lat, lookAround_lng){ /* no way to update coordinate of existing look around object, have to
Jan ’26
Reply to iOS 26 WKWebView STScreenTimeConfigurationObserver KVO Crash
What is happening This crash is happening because the update queue utilized for STScreenTimeConfigurationObserver in WebKit is concurrent instead of serial. See the highlighted line introduced in WebKit. How to fix (suggestions) a) The quick path is for WebKit to utilize the main queue or a private serial one instead of a global concurrent. b) Additionally the ScreenTime framework should either not allow concurrent queues to be utilized in STScreenTimeConfiugurationObserver.init(updateQueue:) or support concurrent queues. Why is this happening TL;DR [STScreenTimeConfigurationObserver setConfiguration:] is getting called multiple times at once and the KVO code is not thread safe. The Details The Automatic KVO implementation for STScreenTimeConfigurationObserver is not thread safe. While STScreenTimeConfiguration is. This issue can be reproduced by concurrently setting the private method [STScreenTimeConfigurationObserver setConfiguration: configuration] to a new configuration. In the implementation of
Topic: UI Frameworks SubTopic: UIKit Tags:
Jan ’26
Reply to SpriteKit scene used as SCNView.overlaySKScene crashes due to SKShapeNode
Ok, so just to make things clear, is it expected that whenever I want to change the SpriteKit scene and also avoid concurrently accessing objects that may be changed in the current thread, I have to queue the SpriteKit changes by capturing all the needed state? It's just surprising to me that this is needed when SpriteKit is used as an overlay in SceneKit, but when running SpriteKit alone, it doesn't seem to be needed. I filed at least one feedback recently about crashes happening only when SpriteKit is used as SCNView.overlaySKScene. Is it expected that one has to use this... boilerplate code when embedded in SceneKit? Couldn't one do without it by simply overlaying a SkView on top of SCNView? class SceneController { private var shapeNode: SKShapeNode! func main() { let shapePath = CGPath(rect: CGRect(x: 0, y: 0, width: 10, height: 10), transform: nil) GameViewController.shared.updateSpriteKit { [shapeNode, shapePath] in shapeNode!.path = shapePath shapeNode!.fillColor = .systemRed } } } class GameV
Topic: Graphics & Games SubTopic: SpriteKit Tags:
Jan ’26
WKWebView + Bluetooth Keyboard: Ctrl+Home / Ctrl+End causes app crash after input blur (iPadOS 18.4.1 / 18.6.2)
1. Summary In a hybrid iOS app using WKWebView (Angular + Capacitor), after programmatically blurring an element and connecting a Bluetooth keyboard, pressing Ctrl+Home or Ctrl+End causes the app to crash. The crash stack shows the issue occurs inside UIKit keyboard handling (UITextInteractionSelectableInputDelegate _moveToStartOfLine), indicating a system-level bug. 2. Steps to Reproduce Open the hybrid app containing a WKWebView. Blur the input (programmatically). Connect a Bluetooth keyboard. Press Ctrl + Home or Ctrl + End. Expected result: No crash. The command should be ignored if no text input is active. Actual result: App crashes immediately. 3. Crash Log (Crashlytics Trace) Crashed: com.apple.main-thread 0 WebKit 0xfbdad0 + 236 1 UIKitCore 0x10b0548 -[UITextInteractionSelectableInputDelegate _moveToStartOfLine:withHistory:] + 96 2 UIKitCore 0xd0fb38 -[UIKBInputDelegateManager _moveToStartOfLine:withHistory:] + 188 3 UIKitCore 0xa16174 __158-[_UIK
Replies
1
Boosts
0
Views
193
Activity
Feb ’26
LLDB assertion failure when debugging Swift app
While debugging a Swift application in Xcode, LLDB crashes with an assertion failure related to LLDBMemoryReader and pointer authentication. The issue occurs during normal debugging (e.g. inspecting variables or stack frames), and causes the debugger to become unusable. The error appears to be triggered inside the Swift language runtime reflection path in LLDB error: Assertion failed: (LLDBMemoryReader module to address map ran into pointer authentication mask!), function addModuleToAddressMap, file /AppleInternal/Library/BuildRoots/603ae698-b099-11ef-b64c-aabfac210453/Library/Caches/com.apple.xbs/Sources/lldb/llvm-project/lldb/source/Plugins/LanguageRuntime/Swift/LLDBMemoryReader.cpp, line 537 Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it): 0 LLDB 0x00000001240eb8f8 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 40 1 LLDB 0x0000000123bbd0a8 lldb_pri
Replies
1
Boosts
0
Views
124
Activity
Feb ’26
Reply to Bug? SwiftData + inheritance + optional many-to-one relationship
I encountered another bug with SwiftData and inheritance and reported it (FB21837287). This one is not related to CloudKit. Briefly, SwiftData crashes during auto-save when the schema contains: A base @Model class with at least one subclass (inheritance) A separate @Model class with a reference to the base class The crash occurs specifically when: There is a class inheritance hierarchy (Beta: Alpha) A separate class (Standalone) has a reference typed as the base class (Alpha?) Changing the reference from var ref: Alpha? to var ref: Beta? (subclass) eliminates the crash.
Replies
Boosts
Views
Activity
Feb ’26
symbolicate crashlog using .symbols files instead of dSYMs
Hi, Some crashes downloaded from TestFlight aren't symbolicated by Xcode and I don't know why, here's an example: Although all uploaded builds contain debug symbols (Symbols directory with .symbols files) and other crashlogs in the same version are symbolicated just fine (also visible on the above SS). I have access only to the .symbols files but not to the original dSYMs and I wonder how to perform symbolication manually. I tried pointing atos and symbolicatecrash utilities to respective .symbols file, but they are unable to work with it. I'm sure it's possible as TestFlight symbolicates crashlogs using only .symbols files somehow. Could you give a hint?
Replies
3
Boosts
0
Views
255
Activity
Feb ’26
Reply to M4 iPadOS stuck at Apple Logo on reboot.
I had the same problem with my M2 iPad Air, and ChatGPT told me to do this instantly worked. but you have to follow the instructions Yes — here’s the clean, repeatable fix for an iPad stuck in a reboot loop (Apple logo → restarts → logo again). Start at Step 1 and only move on if it doesn’t work. ⸻ Step 1 — Force restart (fastest, safest) This fixes temporary system crashes. If your iPad has Face ID (no Home button): 1. Quickly press Volume Up → release 2. Quickly press Volume Down → release 3. Press and HOLD Power 4. Keep holding until you see the Apple logo, then let go If your iPad has a Home button: 1. Hold Home + Power together 2. Keep holding until the Apple logo appears 👉 If it boots normally, you’re done. ⸻ Step 2 — Recovery Mode (most common real fix) Use this if it keeps looping. What you need • A Mac or Windows PC • A cable • Finder (Mac) or iTunes (Windows / older macOS) Steps 1. Connect iPad to the computer 2. Force-restart but DO NOT release when the Apple logo appears 3. Keep holding
Replies
Boosts
Views
Activity
Jan ’26
Reply to NSTextLineFragment crash - how to debug
Thanks for providing the reproducible case, which will greatly help the TextKit folks to address the issue from the framework side. As the reproducible case shows, the crash is triggered by a specific combination of attributes. Unless you can identify the cases and avoid them, I unfortunately don't see anything from the app side that can fix / work around the issue. I have added my comment to the feedback report (FB16905066). Thank you all again for making the feedback much more actionable by providing the project that reproduces the crash. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Jan ’26
Reply to Inserting an NSView (Cocoa) in NSWindowController Views hierarchy
For your first approach, are you able to provide information about the crash, like a crash log? For your second approach, it is common to see initial view hierarchy setup for a window in your window controller subclass’s overridden windowDidLoad method. For a view that just needs to display a solid color, NSBox can be used for this purpose: let box = NSBox() box.boxType = .custom box.borderWidth = 0.0 box.fillColor = NSColor.systemRed
Topic: UI Frameworks SubTopic: AppKit Tags:
Replies
Boosts
Views
Activity
Jan ’26
Reply to Horrible weird Window Server killing bug
This got even weirder. One is that sometimes the use of cos() would cause a compiler error, which was fixed by using Darwin.cos(). This may be fixed in Swift 6.3. The other thing is that in my much more complex code, the crash seemed to be caused by both the cos() call evaluating to 0, but only when the line being drawn with that result had a StrokeStyle applied to it. In anycase, I have filed Feedbacks explaining this, and I'm told the WindowServer team has had it brought to their attention.
Topic: UI Frameworks SubTopic: SwiftUI
Replies
Boosts
Views
Activity
Jan ’26
Inserting an NSView (Cocoa) in NSWindowController Views hierarchy
I have an NSWindowController with several IBOutlets created in storyboard. I want to add an NSView and fill it with some color. I need to place it at a specific position in views hierarchy. I have tried 2 ways, no one succeeds. First. include a custom view in storyboard connect to an IBOutlet in an init of controller, set the layer for the view Result: crash Second build programmatically Result: I do not find where to put this code in the controller code That's basic Cocoa, but way more painful than iOS.
Topic: UI Frameworks SubTopic: AppKit Tags:
Replies
3
Boosts
0
Views
379
Activity
Jan ’26
TUINSRemoteViewController over-release crash in ViewBridge during autorelease pool drain
Summary A crash occurs in ViewBridge framework when a TUINSRemoteViewController object receives -release message after being deallocated. This appears to be a reference counting issue within the ViewBridge framework's internal autorelease pool management. Environment macOS Version: [15.0.0] Application: Custom Qt-based application using Chromium Embedded Framework (xcode version: xcode 15; QT version: 6.5.4 ; CEF version: 138.0.47+g2728d53+chromium-138.0.7204.221) Steps to Reproduce Users are typically using the app normally, but a crash occasionally occurs when they activate and click on the application. This happens infrequently, but it occurs roughly every day. Currently, only a few specific users experience this crash, and it may appear for several consecutive days before disappearing for several days. We cannot reliably reproduce this issue but have collected crash logs from affected users. Crash Analysis Zombie Detection Log: Zombie received -release Dealloc
Replies
1
Boosts
0
Views
231
Activity
Jan ’26
Where did I screw up trying concurrency?
I tried making a concurrency-safe data queue. It was going well, until memory check tests crashed. It's part of an unadvertised git project. Its location is: https://github.com/CTMacUser/SynchronizedQueue/commit/84a476e8f719506cbd4cc6ef513313e4e489cae3 It's the blocked-off method `memorySafetyReferenceTypes' in SynchronizedQueueTests.swift. Note that the file and its tests were originally AI slop.
Replies
2
Boosts
0
Views
272
Activity
Jan ’26
Reply to why mapkit js does not have LookAroundSceneRequest
Ed Ford,  DTS Engineer Your reply does not help. I have look at the sample code thousands times before I ask this question here. The sample code, and document api does not mention how to update coordinate for the look around object. I need constantly change the look around scene coordinate, the sample code only create look around object based on one coordinate. If I need to update coordinate to a different location for this look around object, can you share the sample code to do this job here for everyone that is interested? This is my code, it destroy everytime before create a new one. It works, but it can crash browser webGL if user change coordinate 16 times and above , then it cause apple base map blank. ` // // --- --- apple look around --- // var lookAround var is_lookAround_load_complete = false var is_first_time_lookAround = true // only for 1st time load function create_apple_look_around(lookAround_lat, lookAround_lng){ /* no way to update coordinate of existing look around object, have to
Replies
Boosts
Views
Activity
Jan ’26
Reply to NSTextLineFragment crash - how to debug
Here's a small project to reproduce this TextKit 2 crash inspired by your sample text @Jerrydu: https://github.com/brunosylvain/textkit-2-crash Could you add it to your bug report @macdrevx? Thank you 🙏
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Jan ’26
Reply to iOS 26 WKWebView STScreenTimeConfigurationObserver KVO Crash
What is happening This crash is happening because the update queue utilized for STScreenTimeConfigurationObserver in WebKit is concurrent instead of serial. See the highlighted line introduced in WebKit. How to fix (suggestions) a) The quick path is for WebKit to utilize the main queue or a private serial one instead of a global concurrent. b) Additionally the ScreenTime framework should either not allow concurrent queues to be utilized in STScreenTimeConfiugurationObserver.init(updateQueue:) or support concurrent queues. Why is this happening TL;DR [STScreenTimeConfigurationObserver setConfiguration:] is getting called multiple times at once and the KVO code is not thread safe. The Details The Automatic KVO implementation for STScreenTimeConfigurationObserver is not thread safe. While STScreenTimeConfiguration is. This issue can be reproduced by concurrently setting the private method [STScreenTimeConfigurationObserver setConfiguration: configuration] to a new configuration. In the implementation of
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Jan ’26
Reply to SpriteKit scene used as SCNView.overlaySKScene crashes due to SKShapeNode
Ok, so just to make things clear, is it expected that whenever I want to change the SpriteKit scene and also avoid concurrently accessing objects that may be changed in the current thread, I have to queue the SpriteKit changes by capturing all the needed state? It's just surprising to me that this is needed when SpriteKit is used as an overlay in SceneKit, but when running SpriteKit alone, it doesn't seem to be needed. I filed at least one feedback recently about crashes happening only when SpriteKit is used as SCNView.overlaySKScene. Is it expected that one has to use this... boilerplate code when embedded in SceneKit? Couldn't one do without it by simply overlaying a SkView on top of SCNView? class SceneController { private var shapeNode: SKShapeNode! func main() { let shapePath = CGPath(rect: CGRect(x: 0, y: 0, width: 10, height: 10), transform: nil) GameViewController.shared.updateSpriteKit { [shapeNode, shapePath] in shapeNode!.path = shapePath shapeNode!.fillColor = .systemRed } } } class GameV
Topic: Graphics & Games SubTopic: SpriteKit Tags:
Replies
Boosts
Views
Activity
Jan ’26