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.

Sign up for GitHub

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

Jump to bottom

Potential race condition in get_trace #37

Open
comnik opened this issue Jun 9, 2021 · 0 comments
Open

Potential race condition in get_trace #37

comnik opened this issue Jun 9, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@comnik
Copy link
Contributor

comnik commented Jun 9, 2021 •
edited
Loading

It is currently possible for a thread to access a trace on another thread's pool via get_trace. It could be however, that the owning thread is in the process of growing its thread pool.

We should synchronize get_trace with the pool lock.

Originally identified by @rai-nhdaly
@comnik comnik added the bug Something isn't working label Jun 9, 2021
@NHDaly NHDaly assigned NHDaly and unassigned NHDaly Dec 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@comnik @NHDaly