async-threaded resolver: use ref counter, v2 #16916
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
oops, merge conflict now |
Allocate the data shared between a transfer and an aync resolver
thread separately and use a reference counter to determine its
release.
Change `Curl_thread_destroy()` to clear the thread handle, so
that the thread is considered "gone" and we do not try to join
(and fail to) afterwards.
icing
force-pushed
the
async-thread-ref-count
branch
from
d9fef8e to
cbca09e
Compare
bagder
approved these changes
Apr 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allocate the data shared between a transfer and an aync resolver thread separately and use a reference counter to determine its release.
v2: change
Curl_thread_destroy()to clear the thread handle, so that the thread is considered "gone" and we do not try to join (and fail to) afterwards.