Are you using a custom web server or something like express? What
type/level of caching are you using or did you implement for pages/stores?

This sounds a lot like a closure leak.

- Jeremy

On Wed, Feb 22, 2012 at 8:24 AM, Chris Casey <borochris9@xxxxxxxxx> wrote:

> Unfortunately I know the pattern very well.
> Somewhere in node it is storing all of the served pages.
> memory increasing by the number of pages served.
> Just can't figure out exactly where and how to stop it.
>
> --
> 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 nodejs@xxxxxxxxxxxxxxxx
> To unsubscribe from this group, send email to
> nodejs+unsubscribe@xxxxxxxxxxxxxxxx
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

--
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 nodejs@xxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to
nodejs+unsubscribe@xxxxxxxxxxxxxxxx
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en