remotedialer: segfaults in sync.Pool when calling ClientConnect() #6
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.
Issue: PELEDGE19-3771 - edge-proxy has encountered segmentation fault during runtime due to third party package
logrus
used inremotedialer
. Similar issue could be found here: golang/go#24640. While the issue happens within golang runtime and the problem has been unresolved even for the latest go release.Potential solution: updating module
logrus
to v1.7.0 as it introduces a customized buffer pool API instead of using sync pool from native go lib. Details for the v1.7.0 release could be found hereChanges:
armPelionEdge
->PelionIoT