FS#50676 - nodejs: npm install hangs on Arch's node

Attached to Project: Community Packages
Opened by Gergely (imrehg) - Tuesday, 06 September 2016, 03:09 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 08 September 2016, 14:42 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

From bug reports on the npm and node.js issue trackers, it looks like the Arch-released nodejs 6.5.0 (at least) has some issues compared the ones people get otherwise (e.g. nvm)

https://github.com/npm/npm/issues/13782
https://github.com/nodejs/node/issues/8310

Additional info:
* nodejs 6.5.0
* npm 3.10.3
* Issue does not happen when using node 6.5.0 installed with nvm.

Steps to reproduce:
* Known package.json to trigger it: https://raw.githubusercontent.com/Torwori/ts-mobx-react-starter-kit/8fc30784103b3e152b17a1f242c7745050547c3e/package.json
* run `npm install` in the same directory as the downloaded package.json
* Will stuck at a line similar to this:
`[ .....] - extract:webpack-dev-server: sill doParallel extract 890
Pegs one CPU at 100%, need SIGKILL to stop it.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 08 September 2016, 14:42 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#50614 
Comment by Mike H (yndoendo) - Tuesday, 06 September 2016, 23:07 GMT
Upstream issue has been patched but not committed. Referencing https://codereview.chromium.org/2310513002 and https://github.com/nodejs/node/issues/8310#issuecomment-243054064 as the issue.
Verified npm no longer core dumps / freezes while installing packages by running "npm i -g angular-cli" for verification.
   PKGBUILD (2 KiB)
Comment by Anna Henningsen (addaleax) - Thursday, 08 September 2016, 08:36 GMT
https://codereview.chromium.org/2292953002/ would be the patch for this specific bug, which has been committed in V8. The mentioned patch is just a workaround by adding a compiler flag, which would *not* necessarily also be applied when compiling the copy of V8 coming with Node.

https://github.com/nodejs/node/pull/8411 is the backport for that specific bugfix into the V8 branch that is used by Node, which I have just merged and which will with almost 100 % certainty land in the upcoming Node v6.6.0.

Also, this is a duplicate of https://bugs.archlinux.org/task/49936 – is there any way we (= Node.js) could get notified of downstream bug reports like that? Usually, it would be pretty cool if people could be encouraged to also report problems at the Node issue tracker, even if they appear to only occur on Arch.

Loading...