On Aug 6, 2013, at 3:29 AM, Ronald Wertlen <[email protected]> wrote:
> its the same old suspect, namely references to objects not being cleaned up. > Javascript closures may keep references to objects that can't be GC'ed. You > need to really be aware which refs are long-living and which need to be > cleaned up soon. Shouldn't those cause the heap to grow, too, though? The OP's graphs show that heap growth is relatively flat. -- Brian Lalor [email protected] http://github.com/blalor -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
