You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an established subscription is disposed by calling its dispose function (which is returned by subscribe method itself), which is pretty common scenario, a memory leak occurs in the Client. A listeners field keep track callbacks which will get called when Client.dispose() method is called, but it doesn't properly clean up the callback if the subscription is disposed individually. This leads to constantly growing Client.listeners array if the subscription is frequently created and disposed through application's lifecycle.
The text was updated successfully, but these errors were encountered:
I already met this situation, I'm making an subscription when a modal is open and closing that subscription when that modal is closed, and on the backend the pubs is already complaining that too many listeners added to EventEmitter.
If an established subscription is disposed by calling its dispose function (which is returned by
subscribe
method itself), which is pretty common scenario, a memory leak occurs in theClient
. Alisteners
field keep track callbacks which will get called whenClient.dispose()
method is called, but it doesn't properly clean up the callback if the subscription is disposed individually. This leads to constantly growingClient.listeners
array if the subscription is frequently created and disposed through application's lifecycle.The text was updated successfully, but these errors were encountered: