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
The promise is never triggered. So, after every timeout, a promise will be leaked in the Queue object. Note, the current close function only performs a log statement, so the actual need for a promise in the current codebase.
I discovered this on a device that I think has a dubious network connection (HS300PowerStrip) and numerous children. I did see a couple of tplink-connection objects in memory tied to that IP address, but that may have just been for the children.
The text was updated successfully, but these errors were encountered:
The promise is never triggered. So, after every timeout, a promise will be leaked in the Queue object. Note, the current close function only performs a log statement, so the actual need for a promise in the current codebase.
I discovered this on a device that I think has a dubious network connection (HS300PowerStrip) and numerous children. I did see a couple of tplink-connection objects in memory tied to that IP address, but that may have just been for the children.
The text was updated successfully, but these errors were encountered: