[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386

[Jérémy Lal]

Le lun. 11 févr. 2019 à 20:39, Teemu Ikonen <tpikonen at gmail.com> a écrit :

> Package: npm
> Version: 5.8.0+ds6-3
> Severity: normal
>
> I get a repeatable segfault from npm install by doing the following on
> i386 (deleting the local .npm and node_modules dirs is not needed to
> reproduce).
>
> -*-
>
> $ rm -rf .npm/
> $ rm -rf node_modules/
> $ npm --verbose install electron-spellchecker at 1.1.2
> npm info it worked if it ends with ok
> npm WARN npm npm does not support Node.js v10.15.1
> npm WARN npm You should probably upgrade to a newer version of node as we
> npm WARN npm can't make any promises that npm will work with this version.
> npm WARN npm Supported releases of Node.js are the latest release of 4, 6,
> 7, 8, 9.
> npm WARN npm You can find the latest version at https://nodejs.org/
> npm verb cli [ '/usr/bin/node',
> npm verb cli   '/usr/bin/npm',
> npm verb cli   '--verbose',
> npm verb cli   'install',
> npm verb cli   'electron-spellchecker at 1.1.2' ]
> npm info using npm at 5.8.0
> npm info using node at v10.15.1
> npm verb config Skipping project config: /home/tpikonen/.npmrc. (matches
> userconfig)
> npm verb npm-session 07474421384f9f89
> npm http fetch GET 200 https://registry.npmjs.org/electron-spellchecker
> 259ms
> npm http fetch GET 200 https://registry.npmjs.org/bcp47 118ms
> npm http fetch GET 200 https://registry.npmjs.org/debug 189ms
> npm http fetch GET 200 https://registry.npmjs.org/electron-remote 192ms
> npm http fetch GET 200 https://registry.npmjs.org/@paulcbetts%2fcld 227ms
> npm http fetch GET 200 https://registry.npmjs.org/keyboard-layout 227ms
> npm http fetch GET 200 https://registry.npmjs.org/spawn-rx 104ms
> npm http fetch GET 200 https://registry.npmjs.org/pify 241ms
> npm http fetch GET 200 https://registry.npmjs.org/lru-cache 247ms
> npm http fetch GET 200
> https://registry.npmjs.org/@paulcbetts%2fspellchecker 258ms
> npm http fetch GET 200 https://registry.npmjs.org/debug/-/debug-2.6.9.tgz
> 97ms
> npm http fetch GET 200 https://registry.npmjs.org/rxjs-serial-subscription
> 321ms
> npm http fetch GET 200 https://registry.npmjs.org/pify/-/pify-2.3.0.tgz
> 100ms
> npm http fetch GET 200 https://registry.npmjs.org/rxjs 421ms
> npm http fetch GET 200
> https://registry.npmjs.org/spawn-rx/-/spawn-rx-2.0.12.tgz 204ms
> npm http fetch GET 200 https://registry.npmjs.org/underscore 51ms
> npm http fetch GET 200 https://registry.npmjs.org/glob 54ms
> npm http fetch GET 200 https://registry.npmjs.org/ms 35ms
> npm http fetch GET 200 https://registry.npmjs.org/ms/-/ms-2.0.0.tgz 42ms
> npm http fetch GET 200 https://registry.npmjs.org/lodash.get 51ms
> npm http fetch GET 200 https://registry.npmjs.org/xmlhttprequest 57ms
> npm http fetch GET 200 https://registry.npmjs.org/hashids 68ms
> npm http fetch GET 200 https://registry.npmjs.org/symbol-observable 33ms
> npm http fetch GET 200 https://registry.npmjs.org/nan 49ms
> npm http fetch GET 200 https://registry.npmjs.org/event-kit 59ms
> npm http fetch GET 200 https://registry.npmjs.org/yallist 36ms
> npm http fetch GET 200 https://registry.npmjs.org/pseudomap 43ms
> npm http fetch GET 200
> https://registry.npmjs.org/yallist/-/yallist-2.1.2.tgz 36ms
> npm http fetch GET 200 https://registry.npmjs.org/lodash.assign 39ms
> npm verb correctMkdir /home/tpikonen/.npm/_locks correctMkdir not in
> flight; initializing
> npm verb makeDirectory /home/tpikonen/.npm/_locks creation not in flight;
> initializing
> npm verb lock using
> /home/tpikonen/.npm/_locks/staging-1ec0d591837db4e7.lock for
> /home/tpikonen/node_modules/.staging
> npm http fetch GET 200
> https://registry.npmjs.org/hashids/-/hashids-1.2.2.tgz 316ms
> npm http fetch GET 200
> https://registry.npmjs.org/pseudomap/-/pseudomap-1.0.2.tgz 313ms
> npm http fetch GET 200
> https://registry.npmjs.org/event-kit/-/event-kit-2.5.3.tgz 320ms
> npm http fetch GET 200
> https://registry.npmjs.org/lodash.get/-/lodash.get-4.4.2.tgz 316ms
> npm http fetch GET 200
> https://registry.npmjs.org/symbol-observable/-/symbol-observable-1.0.1.tgz
> 322ms
> npm WARN tar write after end
> npm http fetch GET 200
> https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz
> 497ms
> Segmentation fault.] / extract:brace-expansion: sill extract
> brace-expansion at 1.1.11 extracted to
> /home/tpikonen/node_modules/.staging/brace-expansion-3f1cd090
>
> -*-
>
> On repeated runs the package being extracted is not always the same, but
> the segfault happens when the first package is extracted.
>
> This bug is probably not in npm, but in the interpreter. I'll let you
> sort that out though.


Do you get some log in  ~/.npm ?
Since nodejs has a test suite, and since it crashes when extracting tgz,
obvious culprit is node-tar, but i can't shoot something blindly if i don't
have a (javascript) stack trace.

Jérémy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20190211/6c04e50b/attachment.html>