Fix infinite loop caused by TLS Handler(Only .NET6)#583
Merged
Conversation
Fix infinite loop caused by disconnection during TLS handshake, and the memory exploded instantly.
Contributor
Author
|
.NET 6.0.202 has avoided (not fixed) this problem, and read operations on closed connections will throw exception, as in versions prior to .NET 6 |
|
I have same question with this.Can i use .netcore 3.1 to fix this problem? |
Contributor
Author
YES, Or update to the latest version .NET 6(>=6.0.202) |
I had the same problem with version .NET 6(6.0.5.31213).Now i downgrade to .net core 3.1(3.1.25), It didn't seem to reappear again. |
Contributor
|
I would be very helpful is this could get merged in. Ran into this issue the other day. |
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
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.
Fix infinite loop caused by TLS Handler, and the memory exploded instantly.