On Sat, Jun 29, 2013 at 2:58 PM, Kurt Blackwell <[email protected]> wrote: > Hi all, > > I'm just wondering if there's a way of debugging Node's internal work queue, > like finding out how many setTimeout()s are waiting, or what network > connections are preventing Node from closing. Ideally I would see the > callback associated with them.
There's process._getActiveHandles() and process._getActiveRequests(). Timers are problematic. They don't usually have a one-to-one mapping with a libuv handle so process._getActiveHandles() won't report them. > Most npm packages seem to have poor error handling, and often fail to close > all their resources properly. Surely there must be a way to debug these? > > Thanks for your help. -- -- 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.
