SnapChat Node Mem leak? about node-red-nodes HOT 6 CLOSED

This seems to only really propogate enough to be noticable when running the node every 10 seconds via an inject. Unsure whether it is something to do with the client login being carried out every time there is an "input" which needs to be killed off once the input scripts have run or whether it is down to my shoddy use of variables.

from node-red-nodes.

I still can't find the leak in this code anyone able to take a look? I'm wondering if its a Pi issue? @dceejay fancy doing my work for me? =p

from node-red-nodes.

which version of node? I think there's a known potential memory leak with one of the versions of node (0.10.+?)

from node-red-nodes.

Yea I'm on 1.10. I'll have to downgrade and test again

from node-red-nodes.

One thought.... (as well as the known leak Andy pointed out)
you call login every time round - I know you also call clear - but as the underlying npm is not exactly well documented and doesn't talk to a supported API - who knows if it really cleans up after itself every time... may be better to login once (on node creation) and then reuse the same client instance - unless there is some reason not to ? eg timeout which may then make you re-login anyway ;-)

PS you should also add the required Apache license headers to the files.

from node-red-nodes.

This is a node version issue and not a snapchat issue per-say. It does not seem to escalate out of hand on v0.8 and the garbage collector tidies up correctly.

from node-red-nodes.