Fix crash during shutdown after unsuccessful ping() #8674
Merged
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
AlexPeshkoff
approved these changes
Jul 30, 2025
dyemanov
added a commit
that referenced
this pull request
Jul 30, 2025
dyemanov
added a commit
that referenced
this pull request
Jul 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
If Y-valve's
ping()gets an error from the underlying provider, it disconnects immediately and clears thenextpointer.YHelper::release()callsdestroy()only ifnext != nullptr. Thus the attachment handle remains uncleared from theattachmentsarray. When shutdown is performed afterwards, it iterates through this array and tries to shutdown/release the already destroyed attachment.