[R4R] fix: memory leak issue with diff protocol#1019
Merged
unclezoro merged 1 commit intobnb-chain:developfrom Jul 26, 2022
Merged
[R4R] fix: memory leak issue with diff protocol#1019unclezoro merged 1 commit intobnb-chain:developfrom
unclezoro merged 1 commit intobnb-chain:developfrom
Conversation
unclezoro
approved these changes
Jul 26, 2022
forcodedancing
approved these changes
Jul 26, 2022
Contributor
|
LGTM |
This was referenced Jul 28, 2022
Merged
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.
Description
broadcastDiffLayersis not properly closed, the memory accumulates too many resources and causes OOM.Rationale
broadcastDiffLayerswill be started inNewPeer; need to callpeer.ClosewhenRunPeerfails. otherwise, this goroutine will not be closed.Example
panic.log
Changes
Notable changes:
peeron failure inRunPeerfunction.