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

fdleakcheck

v0.0.1

Published

check for file descriptor leaks

Downloads

6

Readme

node-fdleakcheck: check for file descriptor leaks

This Node module provides primitives for taking a snapshot of open file descriptors and comparing two snapshots to determine if there's been a file descriptor leak.

The implementation is specific to SunOS systems (including SmartOS, OmniOS, and Solaris), as it relies on proc(4) for correctness and pfiles(1M) for human-readable output.

This implementation also depends on child processes (ls, bash, and pfiles). It's possible to check for fd leaks without this, but not without observing the leak checker itself. This module opts for avoiding opening any files itself during the leak check.

Synopsis

var fdleakcheck = require('fdleakcheck');
var fdsBefore;
fdleakcheck.snapshot(function (err, snapshot) {
        if (err) {
                console.error('failed to check fd leaks: %s', err.message);
                return;
        }

        fdsBefore = snapshot;
        /* proceed with operation */
        /* ... */
        /* some time later, after operation */
        fdleakcheck.snapshot(function (err2, fdsAfter) {
                if (err2) {
                        console.error('failed to check fd leaks: %s',
                            err2.message);
                        return;
                }

                if (fdsBefore.differs(fdsAfter)) {
                        console.error('leaks found!');
                        console.error('fds open before:');
                        console.error(fdsBefore.openFdsAsString());
                        console.error('fds open after:');
                        console.error(fdsAfter.openFdsAsString());
                } else {
                        console.error('no leaks found');
                }
        });
});

Errors indicate problems creating the snapshot. Leaks are not turned into Errors. It's up to you to use differs to compare two snapshots to see if there's a leak.

Your program should not be doing anything with file descriptors while a snapshot() operation is oustanding. If it is, the results of the snapshot are undefined.

Contributions

Contributions welcome. Code should be "make prepush" clean. To run "make prepush", you'll need these tools:

  • https://github.com/davepacheco/jsstyle
  • https://github.com/davepacheco/javascriptlint

If you're changing something non-trivial or user-facing, you may want to submit an issue first.