Abstract: A system creates and monitors virtual threads within a node.js application. Callbacks executing within an event loop for a node.js system are identified and may be traced. The callbacks are associated with a context, and resources associated with execution flow during each context may be identified. Callback registrations, callback calls, and callback completion messages may each be detected and recorded. Each registration, call, and completion message is associated with a virtual thread or other transaction identifier. The timing information for each virtual thread and other resource usage for each context may then be identified, stitched together for distributed transactions and reported to a user to provide more detail for node.js application processing.

Abstract: A system detects memory leaks in Node.JS applications. The memory leaks are associated with lines of code rather than particular objects. Lines of code associated with a memory leak is identified by object allocation tracking. Object allocation for lines of code is tracked. A heap snapshot may be captured at the same time at which the object allocation occurs. The results of the object allocation are processed, including removal of objects cleaned up by garbage collection. Objects remaining in the object allocation results are then searched for the end heap snapshot. For objects found in the heap snapshot, the corresponding lines of code that generate the objects are reported to administrators the application.

Abstract: A system creates and monitors virtual threads within a node.js application. Callbacks executing within an event loop for a node.js system are identified and may be traced. The callbacks are associated with a context, and resources associated with execution flow during each context may be identified. Callback registrations, callback calls, and callback completion messages may each be detected and recorded. Each registration, call, and completion message is associated with a virtual thread or other transaction identifier. The timing information for each virtual thread and other resource usage for each context may then be identified, stitched together for distributed transactions and reported to a user to provide more detail for node.js application processing.