dylang/npm-check

Memory leak?

Open

#103 opened on Mar 31, 2016

View on GitHub
 (9 comments) (7 reactions) (0 assignees)JavaScript (6,438 stars) (278 forks)batch import
help wantedissue is in a dependency

Description

Running npm-check reserved all the available RAM + ~15 GB of swap. Running this freezes my computer within seconds.

Contributor guide

Tech stack
javascriptnodejs
Domain
clitooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Node.jsMemory profilingJavaScript debugging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
The issue reports a memory leak causing high RAM and swap usage. To reproduce, run npm check on a large project with many dependencies. Investigate by profiling with Node.js heap dump tools. Look at the core logic in index.js or similar for potential circular references or unbounded arrays. Check open source forks or comments for any identified root cause. Consider adding a memory limit or streaming output to reduce memory usage.