Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-13841] Perf Incorrectly Assigns Dispatch Calls #608

swift-ci opened this issue Nov 10, 2020 · 1 comment

[SR-13841] Perf Incorrectly Assigns Dispatch Calls #608

swift-ci opened this issue Nov 10, 2020 · 1 comment


Copy link

@swift-ci swift-ci commented Nov 10, 2020

Previous ID SR-13841
Radar rdar://problem/71271956
Original Reporter xanderai (JIRA User)
Type Bug

Attachment: Download


This was run on Ubuntu 18.04 with Swift for Tensorflow 0.10:


$ swift --version
Swift version 5.3-dev (LLVM 55d27a5828, Swift 6a5d84ec08)
Target: x86_64-unknown-linux-gnu
$ which swift


I don't believe it's specific to Swift for Tensorflow.

Additional Detail from JIRA
Votes 0
Component/s libdispatch
Labels Bug
Assignee None
Priority Medium

md5: 5c2364057133aadaf7ecfa69ab055195

Issue Description:

This is based on the Swift Forums discussion here.

Find attached a screenshot of a perf flamegraph that was captured on 8 hours of a Swift server that uses Swift NIO and serial async DispatchQueues. Notice that everything above the `_dispatch_call_block_and_release` is occurring on the serial DispatchQueues. We think those call stacks are not actually executing on NIO's threads, but have been incorrectly assigned to them by perf. It seems like dispatch is missing some debug symbols, which prevents perf getting an accurate handle on how we get into `_dispatch_call_block_and_release`.

This flame graph was collected using the instructions here.

![](Screen Shot 2020-11-08 at 22.30.34.png)

Copy link

@Lukasa Lukasa commented Nov 11, 2020

@swift-ci create

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants