Yes I'm using shift() to remove them from the queue. Like I say, detailed examination of my objects, queues etc using node-inspector confirms that they're being managed and clearing down correctly.
The stuff Chris discovered building up in memory seems to be "behind the scenes" within Node (or perhaps V8) itself and not in any of my Javascript logic Rob On Feb 24, 12:15 pm, mscdex <[email protected]> wrote: > On Feb 24, 3:43 am, rtweed <[email protected]> wrote: > > > Adding to the queue triggers an event to process the queue, and the > > request is dispatched to the first available child process. Back > > comes the generated response content, triggering "data" events in my > > handler for the childProcess.stdout. When a terminating sequence is > > detected, the response is sent back to the browser that requested it. > > This is done via an index value that is returned by the child process > > along with the content payload, the index points to the queuedRequest > > object which contains the response object. I then dispatch the > > response, using: > > > queuedRequest.response.writeHead(httpStatus, headers); > > queuedRequest.response.write(bodyStr); > > queuedRequest.response.end(); > > Are you sure you're properly removing requests from the queue (via > pop() or shift()) and not just referencing it by index? -- 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
