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

Race Condition Between Thread Destructor and Pool Destroy in Scalable Pool #933

Open
lplewa opened this issue Nov 25, 2024 · 2 comments
Open

Race Condition Between Thread Destructor and Pool Destroy in Scalable Pool #933

lplewa opened this issue Nov 25, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@lplewa
Copy link
Contributor

lplewa commented Nov 25, 2024

A race condition occurs when the scalable pool is destroyed while another thread is performing Thread-Local Storage (TLS) destruction. This issue arises only if one thread is in its TLS destructor and another thread calls umfPoolDestroy. There is no problem when a thread is destructed after the pool has been destroyed.
@lplewa lplewa added the bug Something isn't working label Nov 25, 2024
@vinser52
Copy link
Contributor

Do you have a reproducer?

@lplewa
Copy link
Contributor Author

lplewa commented Dec 2, 2024

Do you have a reproducer?

Only as #899 - you have to remove sleep which i added to workaround this issue.

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
@vinser52 @lplewa