Your message dated Sat, 15 Sep 2018 18:35:08 +0530
with message-id <[email protected]>
and subject line Re: npm search runs out of memory
has caused the Debian Bug report #840640,
regarding npm search runs out of memory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
840640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840640
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: npm
Version: 1.4.21+ds-2
Severity: normal

When running npm search it appeared to run out of memory while building
its index. I was monitoring it in top and the memory usage seemed to be
fairly stable at 23.x% (of 8GB) rather than steadily climbing. Perhaps
node is imposing a limit to keep overall use below 2GB?

Output:

$ npm search minimatch
npm WARN Building the local index for the first time, please be patient

<--- Last few GCs --->

  137285 ms: Scavenge 1393.4 (1449.8) -> 1393.4 (1449.8) MB, 3.2 / 0 ms
[allocation failure].
  137289 ms: Scavenge 1393.4 (1449.8) -> 1393.4 (1449.8) MB, 3.0 / 0 ms
[allocation failure].
  137292 ms: Scavenge 1393.4 (1449.8) -> 1393.4 (1449.8) MB, 3.0 / 0 ms
[allocation failure].
  138179 ms: Mark-sweep 1393.4 (1449.8) -> 1392.9 (1449.8) MB, 887.8 / 0
ms [last resort gc].
  139082 ms: Mark-sweep 1392.9 (1449.8) -> 1393.1 (1449.8) MB, 902.8 / 0
ms [last resort gc].


<--- JS stacktrace --->

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

Security context: 0x6def95b4629 <JS Object>
    1: stringify [native json.js:157] [pc=0x1681a58539e4]
(this=0x6def95ac529 <a JSON with map 0x3769ecd09851>,u=0x23c6d6a1da49
<an Object with map 0x2209ac37a8c9>,v=0x6def95041b9
<undefined>,I=0x6def95041b9 <undefined>)
    2: arguments adaptor frame: 1->3
    3: /* anonymous */
[/usr/share/npm/node_modules/npm-registry-client/lib/get.js:100]
[pc=0x1681a583d317] (this=0x650e961c479 <JS Global O...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of
memory
Aborted
$ 


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages npm depends on:
ii  node-abbrev               1.0.9-1
ii  node-ansi                 0.3.0-2
ii  node-ansi-color-table     1.0.0-1
ii  node-archy                0.0.2-1
ii  node-block-stream         0.0.7-1
ii  node-fstream              0.1.24-1
ii  node-fstream-ignore       0.0.6-2
ii  node-github-url-from-git  1.4.0-1
ii  node-glob                 4.0.5-1
ii  node-graceful-fs          3.0.2-1
ii  node-gyp                  3.4.0-1
ii  node-inherits             2.0.1-3
ii  node-ini                  1.1.0-1
ii  node-lockfile             0.4.1-1
ii  node-lru-cache            2.3.1-1
ii  node-minimatch            1.0.0-1
ii  node-mkdirp               0.5.0-1
ii  node-nopt                 3.0.6-1
ii  node-npmlog               0.0.4-1
ii  node-once                 1.1.1-1
ii  node-osenv                0.1.0-1
ii  node-read                 1.0.5-1
ii  node-read-package-json    1.2.4-1
ii  node-request              2.26.1-1
ii  node-retry                0.6.0-1
ii  node-rimraf               2.2.8-1
ii  node-semver               2.1.0-2
ii  node-sha                  1.2.3-1
ii  node-slide                1.1.4-1
ii  node-tar                  1.0.3-2
ii  node-underscore           1.8.3~dfsg-1
ii  node-which                1.0.5-2
ii  nodejs                    4.3.1~dfsg-3

npm recommends no packages.

npm suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
On Thu, 13 Oct 2016 14:58:35 +0100 Tony Houghton <[email protected]> wrote:
> Package: npm
> Version: 1.4.21+ds-2
> Severity: normal
>
> When running npm search it appeared to run out of memory while building
> its index. I was monitoring it in top and the memory usage seemed to be
> fairly stable at 23.x% (of 8GB) rather than steadily climbing. Perhaps
> node is imposing a limit to keep overall use below 2GB?

Closing old bug. If stiill relevant on npm 5.8.0, please open another bug.

--- End Message ---
-- 
Pkg-javascript-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to