I had a bit of a look at that ... could be handy to see whats keeping
a process running (how did you use it? periodically poll it and output
the details?)

On Jan 17, 12:05 am, Forrest L Norvell <[email protected]> wrote:
> On Tue, Jan 15, 2013 at 10:57 PM, Jake Verbaten <[email protected]> wrote:
> > +1 for the "tell me what is spinning on the event loop not closing this
> > test" module. Someone should write that.
>
> If you're running Node 0.8+ (and why aren't you, if not?), you can use two
> internal API calls on the process object, process._getActiveHandles() and
> process._getActiveRequests(), to cough up lists of unexpired timer handles
> and pending requests that are preventing the main event loop from shutting
> down. They're not the friendliest interfaces, but that hasn't kept me from
> using them to deal with a bunch of subtle issues in the past.
>
> No C++ needed!
>
> F

-- 
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

Reply via email to