Search results for

LLDB crash

29,562 results found

Post

Replies

Boosts

Views

Activity

Collection Reusable View Added Via Storyboard Not Registering with the Collection View
When I set up a UICollectionReusableView cell in storyboard and try to dequeue a cell of this type, my app crashes with this error message: Steps I've gone through to add my collection reusable view in storyboard: I added a collection reusable view by dragging the item from the panel of objects to my collection view. I created a class called EmotionFiltersHeaderView which subclasses UICollectionReusableView that contains a reference to an IBOutlet var for the label I added to the reusable view (also in storyboard). I changed the class name of the reusable view in the storyboard to my custom class name, EmotionFiltersHeaderView. I added an identifier to the reusable view and called it emotionFiltersHeaderReusableView. I've included the header view in the boundary supplementary items property of the section where I'm adding the header view. This is my code: `let headerSize = NSCollectionLayoutSize(widthDimension: .fractionalWidth(1.0), heightDimension: .estimated(37.0)) let header = NSCollectionLayoutB
Topic: UI Frameworks SubTopic: UIKit
4
0
78
Jul ’25
Reply to pas_panic_on_out_of_memory_error crash on tvOS 15.4 and 15.4.1
[quote='847039022, laesde, /thread/704718?answerId=847039022#847039022, /profile/laesde'] I can’t lock up the ips log files in Xcode Organizer. [/quote] Understood. Honestly, I don’t think getting more crash reports is going to help you here, and you’d be better off investing that time in trying to reproduce the issue. Clearly it’s a common problem, and Apple TV has a pretty limited configuration space, so this is more feasible than it would be, say, if this were happening on a Mac. First, survey your crash reports to see if they tell you anything about the device spread. The crash report you posted is from AppleTV6,2, that is, Apple TV 4K (1st generation). Are they all from that? Or are you seeing crashes from more modern Apple TVs. Similarly, do this analysis for the tvOS version spread. Also look at the app lifespan. In your crash the app had been running for 20-ish minutes. Is that typical? A memory problem like this is more likely to show up the longer the app
Topic: Safari & Web SubTopic: General Tags:
Jul ’25
Reply to Crash in libswiftCore with swift::RefCounts
I’m glad to hear you’re making progress. [quote='847078022, FT-cfoy, /thread/791083?answerId=847078022#847078022, /profile/FT-cfoy'] The completion handler is spinning up a new thread [/quote] I noticed that the crashing code is being called out of Network framework. One thing to watch out for there is the type of queue that you pass into Network framework when you create your NWConnection [1]. Network framework will accept either a serial queue or a concurrent queue. Internally it does its own serialisation, so it doesn’t care. However, for your own sanity it’s important to use a serial queue. If you use a concurrent queue, it becomes very hard to reason about your code. Similarly, if you have multiple connections running simultaneously, it often makes sense to use the same serial queue for all of them. Oh, and be wary of concurrent queues in general. See Avoid Dispatch Global Concurrent Queues. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @
Topic: Programming Languages SubTopic: Swift Tags:
Jul ’25
Using Processor Trace on Non-Xcode Built Binary
Hiya folks! I'm David and I work on rust-analyzer, which is a language server for Rust similar to sourcekit-lsp. I'm using the new Instruments profiling tooling functionality in Xcode 16.3 and Xcode 26 (Processor Trace and CPU Counters) to profile our trait solver/type checker. While I've been able to use the new CPU Counters instrument successfully (the CPU Bottleneck feature is incredible! Props to the team!), I've been unable to make use of the Processor Trace instrument. Instruments gives me the error message Processor Trace cannot profile this process without proper permissions. The diagnostic suggests adding the com.apple.security-get-task-allow entitlement to the code I'm trying to profile, or ensure that the build setting CODE_SIGN_INJECT_BASE_ENTITLEMENTS = YES is enabled in Xcode. Unfortunately, I don't know how I can add that entitlement to a self-signed binary produced by Cargo and I'm not using Xcode for somewhat obvious reasons. Here's some information about my setup: Instruments Version 26.0 (1
5
0
372
Jul ’25
Why Large-Scale Model Scenes Cause Real Device Crashes
Is there any limitation in Vision Pro when loading scenes with large-scale models? Test Case: Asset: Composite USDA file containing 10 individual models (total triangles count: ~4.2M) Simulator: Loads and renders correctly Real Device: Loads asset successfully but failure during rendering phase: Environment abruptly dims System spontaneously reboots How can we resolve this issue? Below are excerpted logs preceding the crash: <<<< FigAudioSession(AV) >>>> audioSessionAVAudioSession_CopyMXSessionProperty signalled err=-19224 (kFigAudioSessionError_UnsupportedOperation) (getMXSessionProperty unsupported) at FigAudioSession_AVAudioSession.m:606 Attempted to add ornament: ; rotation: {{0, 0, 0}, 0}; opacity: 1.000000; canFollowUser: YES; effectiveOffset: {0, 0, 0}; presentingViewController: 0x0; billboardingBehavior: 0x0; scalingBehavior: 0x0; relativeToParent: NO; nonHeritableDepthDisplacement: 0.000000; order: 0.000000; _window._determinedSize: {0, 0}; _window: (null)> to nil
1
0
143
Jul ’25
Reply to Crash in libswiftCore with swift::RefCounts
2025-06-09_18-48-03.1721_-0600-43bc27c538c2f93348a83e5380b5f016cc859f71.crash Thanks Quinn! I'm attaching one of the crash logs here. However your pointer got me to the issue - it's a race condition when the device is getting lots of messages over UDP from lots of other disparate devices and those messages are getting split over multiple packets. The completion handler is spinning up a new thread, but working off of the same instance of an underlying class which is where I think the issue is. I was able to replicate it by flooding the device with a bunch of partial messages randomly and could easily reproduce.
Topic: Programming Languages SubTopic: Swift Tags:
Jul ’25
Reply to A Summary of the WWDC25 Group Lab - Developer Tools
(continued from above) Swift Testing is great for unit tests, but I was hoping there would be some love this year to improve the way UI tests are written and structured too. Is this something we can expect this year? Xcode 26 contains improvements to how you can record the actions for your UI test, and select the element queries that drive the UI test through the XCTest APIs. Our session Record, replay, and review: UI automation with Xcode is a great resource to understand the new improvements to these testing workflows. Are the new Icon Composer files backward compatible with previous OSes and Xcode will take care of that or do we need to also keep the old AppIcon? Yes, icons made with Icon Composer will automatically create a pre-composited bitmap icon during the build process that supports previous OS versions. Are there new debugging tools in Xcode that help developing with Swift Concurrency? Yes, there are lots of improvements under the hood in Xcode 26! They include following async tasks across threads
Jul ’25
Reply to Background App Refresh
The app no longer crashes, but with my current configuration, the task does not run. I initialize the task scheduler in the App file's init() function, which calls handleAppRefresh(), which calls RefreshAppContentsOperation()At a given time I call scheduleAppRefresh(), which I thought would preform the task at the scheduled time. The function runs and prints this: All of these functions referenced are in my post above. I tried implementing a queue by doing this: let queue = OperationQueue() let operation = RefreshAppContentsOperation() queue.addOperation(operation) How can I resolve this by Queue or .task?
Jul ’25
Reply to Files App Share Context with Security scoped resource fails
First off, a warning on ANY usage of URL.path() and string-based paths in general. Basically, the existence of string paths in our API is a fundamental design mistake we made 25+ years ago and have been paying for ever since. The issue isn't all that visible because actually relying on normalization sensitivity is a fairly terrible idea, not because the system actually handles this case properly. In addition, there are places in our API like file iteration where the path variant is MUCH worse than the URL equivalent. In any case, I recommend avoiding string paths wherever possible. Kevin, this is helpful information. Just to make sure I'm reading you correctly, is it a valid approach to copy the file into your sandboxed app directory (e.g. the app's documents folder) to Quick Look, and then remove it once you're done with Quick Look? Yes, but with the qualifiers: Things get a lot more complicated if/when you're crossing volumes, something which isn't necessarily obvious without a lot of additional checking. Y
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’25
Reply to pas_panic_on_out_of_memory_error crash on tvOS 15.4 and 15.4.1
@DTS Engineer Unfortunately, that crash is our top crash on production and I can’t lock up the ips log files in Xcode Organizer. Our application still relies on TVMLKit so one context is used by me directly. About the second one, I suspect that a third-party framework, such as SmartLib_tvOS, is also using that for its own purposes. thread 16: 11 JavaScriptCore 0x00000001ad6880b8 llint_call_javascript + 8 12 JavaScriptCore 0x00000001acc6692c JSC::Interpreter::executeCall(JSC::JSObject*, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 904 (Interpreter.cpp:1299) 13 JavaScriptCore 0x00000001ac504224 JSObjectCallAsFunction + 752 (JSObjectRef.cpp:740) 14 JavaScriptCore 0x00000001ac4770d0 -[JSValue callWithArguments:] + 364 (JSValue.mm:643) 15 SmartLib_tvOS 0x00000001056c1848 0x1056b8000 + 38984 16 Foundation 0x0000000197a5e320 __NSThread__start__ + 716 (NSThread.m:991)```
Topic: Safari & Web SubTopic: General Tags:
Jul ’25
Swift/C++ interoperability issue in std::string
In scope of one of our project we've faced an issue with constant crashes when integrating C++ library in Swift code using Swift/C++ interoperability. Investigating the root causes of the issue we've discovered that with new version of Swift bug was introduced. Long story short: for strings bigger than 27 symbols memory is feed incorrectly that causes the crashes. By creating this post I wanted to draw community's attention to the problem and promote it to be solved quicker as for now it is not addressed.
1
0
514
Jul ’25
Reply to Does Core Spotlight work with document-based apps?
Thank you again for the thoughtful response. This is the high-level solution I've ended up with. On the whole, I think this all sounds reasonable. Throwing out a few potential tweaks/details: Search is required for in-app use only; system-wide search is not. If system-wide search would be a nice-to-have, then I suspect you could pull out the important parts (meaning, the details a user might actually search for system-wide) of your app-level indexer and use that to implement CSImportExtension. When a document's URL changes, it updates the domainIdentifier of its searchable items. When you're dealing with long-term file references, you need to think bookmarks, NOT URLs. That's partly because of security scope, but it's mostly because, in practice, file paths have one of the characteristic patterns that is FABULOUS at creating bugs. That is: On any given system, file locations and general configuration are stable enough that the fully path to any given location tends to not change very often. In real-world usag
Topic: App & System Services SubTopic: General Tags:
Jul ’25
Reply to Xcode crashes when saving .intentdefinition file with configuration intent
Translated Report (Full Report Below) Process: Xcode [6971] 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-07-01 18:10:42.9453 +0200 OS Version: macOS 15.5 (24F74) Report Version: 12 Anonymous UUID: 63C6DB2E-A2A0-DDAE-1DC2-8B77CC9535AE Sleep/Wake UUID: 276F6F44-F58B-459D-98EC-81A031BF3334 Time Awake Since Boot: 62000 seconds Time Since Wake: 5081 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [6971] Application Specific Information: abort() called Application Specific Signatures: NSInvalidArgumentException Application Specific Backt
Jul ’25
Xcode crashes when saving .intentdefinition file with configuration intent
Hi everyone, I’m experiencing a consistent crash in Xcode 16.4 (on macOS 15.5 when working with SiriKit .intentdefinition files. 🐛 Issue Whenever I try to add or modify an intent and then hit ⌘S to save, Xcode immediately crashes. This happens both with: Newly created .intentdefinition files Existing ones already linked to a Widget target I’ve tried: Clearing DerivedData Recreating the intent file from scratch Minimal edits (only 1 intent and 1 parameter) Setting correct IntentsSupported in the Info.plist Editing in Xcode and using Target Membership properly Still, Xcode crashes consistently when I save. ⚙️ Environment Xcode: 16.4 macOS: 15.5 Mac: Mac Studio M2 Max ✅ Workaround I’m currently editing the .intentdefinition file manually in source mode or using a text editor, which avoids the crash — but it’s far from ideal. 💬 Question Is anyone else experiencing this? Is there a known fix or workaround that allows safe editing in Interface Builder? Any response from Apple e
1
0
80
Jul ’25