-
-
Notifications
You must be signed in to change notification settings - Fork 231
-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
[bug] Memory leak on client.js 'connect' event #348
Labels
Comments
@srmarjani Try to set |
@srmarjani Did you fixed? Can this be closed? |
Hi |
You right! I think in that case we should queue packets and set connect event in client init, when connected event is fired handle all queued packets (if present)
Daniel
… On 23 Jan 2020, at 13:19, Razi Marjani ***@***.***> wrote:
Hi
I will try to reproduce the bug. because I choose another approach.
But I guess increasing the concurrency is not a solution.
Because concurrency is 100 by default but as you see in warning 11 event on connected event of client make problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
robertsLando
changed the title
(node:16044) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 connected listeners added.
[bug] Memory leak on client.js 'connect' event
Jan 23, 2020
robertsLando
added a commit
that referenced
this issue
Jan 28, 2020
fix: Memory leak on client.js 'connected' event #348
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
I am using mqtt as mqtt client.
In my use case I need to send about 1000 QOS1 packet every 4 second.
every 4 seconds I open a new client by mqtt.connect then I publish 1000 packets by p-map by concurrency 100 and at the end I end connection
But I am encountering below warning at aedes side
And the stack trace is
I think the problem is in this function
Is there any problem in opening and closing the connection to broker?
Thanks
The text was updated successfully, but these errors were encountered: