npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

rf-heapdump

v1.0.0

Published

Make a dump of the V8 heap for later inspection.

Downloads

21

Readme

rf-node-heapdump

Make a dump of the V8 heap for later inspection.

This is a modified version which does not fork or delete the snapshot, so diffing in the chrome inspector should work. Expect to see much higher memory usage.

Install

npm install heapdump

Or, if you are running node.js v0.6 or v0.8:

npm install [email protected]

Build

node-gyp configure build

Usage

Load the add-on in your application:

var heapdump = require('heapdump');

The module exports a single writeSnapshot([filename], [callback]) function that writes out a snapshot. filename defaults to heapdump-<sec>.<usec>.heapsnapshot when omitted.

heapdump.writeSnapshot('/var/local/' + Date.now() + '.heapsnapshot');

The function also takes an optional callback function which is called upon completion of the heap dump.

heapdump.writeSnapshot(function(err, filename) {
  console.log('dump written to', filename);
});

The snapshot is written synchronously to disk. When the JS heap is large, it may introduce a noticeable "hitch".

Previously, node-heapdump first forked the process before writing the snapshot, making it effectively asynchronous. However, it broke the comparison view in Chrome DevTools and is fundamentally incompatible with node.js v0.12. If you really want the old behavior and know what you are doing, you can enable it again by setting NODE_HEAPDUMP_OPTIONS=fork in the environment:

$ env NODE_HEAPDUMP_OPTIONS=fork node script.js

On UNIX platforms, you can force a snapshot by sending the node.js process a SIGUSR2 signal:

$ kill -USR2 <pid>

The SIGUSR2 signal handler is enabled by default but you can disable it by setting NODE_HEAPDUMP_OPTIONS=nosignal in the environment:

$ env NODE_HEAPDUMP_OPTIONS=nosignal node script.js

Inspecting the snapshot

Open Google Chrome and press F12 to open the developer toolbar.

Go to the Profiles tab, right-click in the tab pane and select Load profile....

Select the dump file and click Open. You can now inspect the heap snapshot at your leisure.

Note that Chrome will refuse to load the file unless it has the .heapsnapshot extension.

Caveats

On UNIX systems, the rule of thumb for creating a heap snapshot is that it requires memory twice the size of the heap at the time of the snapshot. If you end up with empty or truncated snapshot files, check the output of dmesg; you may have had a run-in with the system's OOM killer or a resource limit enforcing policy, like ulimit -u (max user processes) or ulimit -v (max virtual memory size).