Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Continuous calls to write() after error may cause memory leaks. #53

Closed
cheatfate opened this issue Oct 7, 2019 · 0 comments
Closed

Continuous calls to write() after error may cause memory leaks. #53

cheatfate opened this issue Oct 7, 2019 · 0 comments

Comments

@cheatfate
Copy link
Collaborator

cheatfate commented Oct 7, 2019 •
edited
Loading

There no checks present in write() procedures for errored transport.
https://github.com/status-im/nim-chronos/blob/master/chronos/transports/stream.nim#L1576
@cheatfate cheatfate changed the title Continuous calls to write() after error/close may cause memory leaks. Continuous calls to write() after error may cause memory leaks. Oct 7, 2019
@mratsim mratsim mentioned this issue Sep 23, 2020
Open
bung87 pushed a commit to bung87/nim-chronos that referenced this issue Nov 17, 2020
@cheatfate
Fix status-im#53
0389659
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cheatfate