-
-
Notifications
You must be signed in to change notification settings - Fork 97
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.
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
Memory leak when using event-emitter interface #217
Labels
Comments
Page-
added a commit
to balena-io/open-balena-vpn
that referenced
this issue
Jul 11, 2022
See: mkozjak/node-telnet-client#217 Change-type: patch
5 tasks
Nice find! Able to fix this asap so Balena doesn't need to be downgraded? |
Page-
added a commit
to balena-io/open-balena-vpn
that referenced
this issue
Jul 11, 2022
See: mkozjak/node-telnet-client#217 Change-type: patch
Page-
added a commit
to balena-io/open-balena-vpn
that referenced
this issue
Jul 11, 2022
See: mkozjak/node-telnet-client#217 Change-type: patch
Page-
added a commit
to balena-io/open-balena-vpn
that referenced
this issue
Jul 11, 2022
See: mkozjak/node-telnet-client#217 Change-type: patch
I do plan to look into a fix but first I need to resolve the issue for balena |
Thanks so much, @Page- ! |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the introduction of ce2bb8e by @kshetline it means that all data is stored in the
pendingData
property and is only removed when you use thenextData()
interface which means that if you instead use the event-emitter interface, eg.on('data', ...)
thenpendingData
will grow indefinitelyThe text was updated successfully, but these errors were encountered: