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
Hi, there,
I recently found that zerorpc.Server instance will cause memory leak, after digged it a little, I found that the code in npmjs.org and github.com is no synced. In the file: lib/channel.js
The judgement refers to this.state, which is always undefined. So the condition will always be false, the code within the block(which delete the used channels) will never be done, thus leading to the memory leak.
The text was updated successfully, but these errors were encountered:
crystaldust
changed the title
Code not synced with npm, which will lead to memory leak.
Code not synced with npm, which will leads to memory leak.
Mar 26, 2015
crystaldust
changed the title
Code not synced with npm, which will leads to memory leak.
Code on npmjs.org is not synced with that on github.com, which will leads to memory leak.
Mar 26, 2015
Hi, there,
I recently found that zerorpc.Server instance will cause memory leak, after digged it a little, I found that the code in npmjs.org and github.com is no synced. In the file:
lib/channel.js
At line 151, code on github:
the code is correct, while at line 150, code on npmjs, the code is:
The judgement refers to this.state, which is always undefined. So the condition will always be false, the code within the block(which delete the used channels) will never be done, thus leading to the memory leak.
The text was updated successfully, but these errors were encountered: