-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[backports-release-1.11] 1.11 Profiling threading fix backports #56358
[backports-release-1.11] 1.11 Profiling threading fix backports #56358
Conversation
…liaLang#55622) Fixes an issue with JuliaLang#55500, where signals may abruptly abort the process as they observe it is still processing the resume SIGUSR2 message and are not able to wait for that processing to end before setting the new message to exit. (cherry picked from commit da3468c)
I forgot about the existence of threads, so had hard-coded this to only support one thread. Clearly that is not sufficient though, so use the semaphore here as it is intended to be used. Fixes JuliaLang#55703 --------- Co-authored-by: Ian Butterworth <i.r.butterworth@gmail.com> (cherry picked from commit 4f0a333)
What should the tests look like? The profiling result is not exactly empty, it does have a few (trivial) things in the flame graph, so what would be a good criterion for a test that fails in the current state of things? |
I'm guessing that if you start with -t8 and do |
I checked on a linux x86 machine with On 1.11.1 only the first thread appears to be sampled.
On this PR all are sampled.
|
SGTM |
0f7f762
into
JuliaLang:backports-release-1.11
Fixes #56327
Needs checking on a linux machine with more than one thread.Confirmed fix. #56358 (comment)