Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

npm outdated --depth 9999 #15393

Closed
3 of 15 tasks
leedm777 opened this issue Jan 4, 2017 · 2 comments
Closed
3 of 15 tasks

npm outdated --depth 9999 #15393

leedm777 opened this issue Jan 4, 2017 · 2 comments

Comments

@leedm777
Copy link

leedm777 commented Jan 4, 2017

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

When a project has circular dependencies (see medikoo/es5-ext#55), npm outdated runs in circles then eventually crashes.

While circular dependencies are arguably a Bad Thing™, other subcommands don't seem to have a problem with it.

How can the CLI team reproduce the problem?

$ npm init -y
$ npm install --save d@1.0.0
$ npm outdated --depth 9999

<--- Last few GCs --->

  111225 ms: Mark-sweep 1351.5 (1434.0) -> 1351.6 (1434.0) MB, 958.2 / 0.0 ms [allocation failure] [GC in old space requested].
  112034 ms: Mark-sweep 1351.6 (1434.0) -> 1351.5 (1434.0) MB, 809.0 / 0.0 ms [allocation failure] [GC in old space requested].
  112864 ms: Mark-sweep 1351.5 (1434.0) -> 1354.4 (1418.0) MB, 829.4 / 0.0 ms [last resort gc].
  113682 ms: Mark-sweep 1354.4 (1418.0) -> 1357.8 (1418.0) MB, 817.3 / 0.0 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x11e333fcfb51 <JS Object>
    1: init [/Users/dlee/.nodenv/versions/6.9.1/lib/node_modules/npm/node_modules/request/request.js:290] [pc=0x34f56a4ad5ce] (this=0x2d058b844fd9 <a Request with map 0x2d123f1197b1>,options=0x2d058b844f09 <an Object with map 0x2d123f119809>)
    2: new constructor(aka Request) [/Users/dlee/.nodenv/versions/6.9.1/lib/node_modules/npm/node_modules/request/request.js:128] [pc=0x34f56a473ec7] (thi...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/Users/dlee/.nodenv/versions/6.9/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/Users/dlee/.nodenv/versions/6.9/bin/node]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Users/dlee/.nodenv/versions/6.9/bin/node]
 4: v8::internal::Factory::NewByteArray(int, v8::internal::PretenureFlag) [/Users/dlee/.nodenv/versions/6.9/bin/node]
 5: v8::internal::Factory::NewCode(v8::internal::CodeDesc const&, unsigned int, v8::internal::Handle<v8::internal::Object>, bool, bool, int, bool) [/Users/dlee/.nodenv/versions/6.9/bin/node]
 6: v8::internal::PropertyAccessCompiler::GetCodeWithFlags(unsigned int, char const*) [/Users/dlee/.nodenv/versions/6.9/bin/node]
 7: v8::internal::NamedLoadHandlerCompiler::CompileLoadNonexistent(v8::internal::Handle<v8::internal::Name>) [/Users/dlee/.nodenv/versions/6.9/bin/node]
 8: v8::internal::NamedLoadHandlerCompiler::ComputeLoadNonexistent(v8::internal::Handle<v8::internal::Name>, v8::internal::Handle<v8::internal::Map>) [/Users/dlee/.nodenv/versions/6.9/bin/node]
 9: v8::internal::LoadIC::UpdateCaches(v8::internal::LookupIterator*) [/Users/dlee/.nodenv/versions/6.9/bin/node]
10: v8::internal::LoadIC::Load(v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Name>) [/Users/dlee/.nodenv/versions/6.9/bin/node]
11: v8::internal::Runtime_LoadIC_Miss(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/dlee/.nodenv/versions/6.9/bin/node]
12: 0x34f569b092a7
13: 0x34f56a4ad5ce
Abort trap: 6

No npm-debug.log generated.

supporting information:

  • npm -v prints: 4.0.5 (also tried with 3.10.10)
  • node -v prints: 6.9.1
  • npm config get registry prints: https://registry.npmjs.org/
  • Windows, OS X/macOS, or Linux?: macOS
  • Network issues:
    • Geographic location where npm was run: Alabama, US
    • I use a proxy to connect to the npm registry.
    • I use a proxy to connect to the web.
    • I use a proxy when downloading Git repos.
    • I access the npm registry via a VPN
    • I don't use a proxy, but have limited or unreliable internet access.
    • None of the above
  • Container:
    • I develop using Vagrant on Windows.
    • I develop using Vagrant on OS X or Linux.
    • I develop / deploy using Docker.
    • I deploy to a PaaS (Triton, Heroku).
    • None of the above
@pralhadstha
Copy link

pralhadstha commented Feb 12, 2017

Any solutions yet for this issue??? I am also facing the same issue.

Edit : I was having the error when i was compiling the less using gulp. It was due to multiple variables was set for the less and the compiler was looping due to that issue. Fixed by removing the duplicate variables.

@npm-robot
Copy link

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants