swift_asyncLet_begin crashed

Question

Created May ’25

Replies 6

Boosts 0

Participants 2

      Crashed: com.apple.root.user-initiated-qos.cooperative

0 libswift_Concurrency.dylib 0x67f40 swift_task_create_commonImpl(unsigned long, swift::TaskOptionRecord*, swift::TargetMetadata<swift::InProcess> const*, void (swift::AsyncContext* swift_async_context) swiftasynccall*, void*, unsigned long) + 528 1 libswift_Concurrency.dylib 0x64d78 swift_asyncLet_begin + 40 2 AAAA 0x47aef28 (1) suspend resume partial function for ActivityContextModule.fetchRecord(startDate:endDate:) + 50786796 3 libswift_Concurrency.dylib 0x60f5c swift::runJobInEstablishedExecutorContext(swift::Job*) + 252 4 libswift_Concurrency.dylib 0x62514 swift_job_runImpl(swift::Job*, swift::SerialExecutorRef) + 144 5 libdispatch.dylib 0x15ec0 _dispatch_root_queue_drain + 392 6 libdispatch.dylib 0x166c4 _dispatch_worker_thread2 + 156 7 libsystem_pthread.dylib 0x3644 _pthread_wqthread + 228 8 libsystem_pthread.dylib 0x1474 start_wqthread + 8

Boost

Answer 1

ZHIMING1 OP

May ’25

AAAA_issue_4c55bf6d04d5f2965b49a1145dd487ea_crash_session_79ac7d63594345e596e84b9f56a00360_DNE_0_v2_stacktrace.txt

here is full crash ips

0

Answer 2

DTS Engineer OP

Apple

May ’25

It’s hard to offer any insight into this based on a third-party crash report. I don’t trust third-party crash reporters in general — see Implementing Your Own Crash Reporter for a detailed explanation as to why — and in this case the crash report doesn’t contain the info necessary to investigate this crash.

My advice is that you remove your third-party crash reporter and try to capture an Apple crash report for this failure. If you’re able to do that, post it here and I’ll take a look. See Posting a Crash Report for more advice about that process.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 3

ZHIMING1 OP

May ’25

@DTS Engineer how to upload ips？ I can not upload file contain ips

0

Answer 4

ZHIMING1 OP

May ’25

crash.ips

0

Answer 5

DTS Engineer OP

Apple

May ’25

Thanks for that.

How reproducible is this? Can you re-create it in your office? Or are you working solely from crash reports coming in from users?

That crash report is from 18.1.1. Are you seeing this on newer systems? If so, is there a specific skew to the crash reports? For example, did it start showing up in specific OS release?

Most crashes that I see within swift_task_create_commonImpl(…) seem to be caused by memory manager issues, often triggered by concurrency problems. If you haven’t done so already, please test your app using the standard memory debugging tools, because they might make this crash show up more reliably, something that’d greatly help with the investigation.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 6

DTS Engineer OP

Apple

May ’25

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits.

Are you suggesting that the issue might be specific to iOS 18.1.1 … ?

No. I mentioned this because, if there’s pattern to the OS versions that are seeing this problem, that might be useful to your investigation. For example:

If you’re not getting crash reports for more modern releases, that suggests that this was an OS bug that we fixed.
But it also means that you’re unlikely to be able to reproduce it because you’re testing on the latest OS release.
If you’re seeing this across a wide range of OS releases, that’s more suggestive of a problem with your code.

is it more likely related to memory management or concurrency?

Well, hard-to-reproduce problems are almost always related to memory management or concurrency (-: The reason why I recommend the standard memory debugging tools is that they are easy to enable and sometimes yield very useful results.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0