Fix Debugger Cpu Load Issue#146
Merged
azimjohn merged 1 commit intoazimjohn:debuggerfrom May 15, 2023
mmkamron:patch-1
Merged
Conversation
Owner
|
Thanks Kamron for your contribution! Since bind() is called bi-directionally, it must have closed both connections in turn. 2.1 binaries will be updates the new changes. |
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
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.
Solves #135.
The issue was reproducible on my Linux machine as well. After running command with
--debugoption and accessing a public endpoint, CPU utilization increases instantly, in my case up to 220%. However, just closing source connection in bind function fixed the issue for me.