We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In a normal use case, during thread destruction, a debug message says already gone.
Do not call kill() in the destructor if it was already called explicitly.
kill()
The text was updated successfully, but these errors were encountered:
Fixed on 2023-05-31.
Sorry, something went wrong.
#80: avoid already gone message
0920f5d
ilg-ul
No branches or pull requests
In a normal use case, during thread destruction, a debug message says already gone.
Do not call
kill()
in the destructor if it was already called explicitly.The text was updated successfully, but these errors were encountered: