Closed agauniyal closed 8 years ago
Also if it's relevant, ember-cli doesn't gets uninstalled propely too -
~ ❯ npm -g uninstall ember-cli
^C^C^CKilled ...] / remove:backo2: sill vacuum-fs quitting because other entries in /home/agau
has been stuck with 100% cpu before I sent SIGKILL manually and then retried it -
^C^C^CKilled ...] / remove:backo2: sill vacuum-fs quitting because other entries in /home/agau
137 ~ ❯ npm -g uninstall ember-cli
[ .......] \ diffTrees: sill install generateActionsToTake
- array-to-sentence@1.1.0 node_modules/ember-cli/node_modules/array-to-sentence
- lodash@3.10.1 node_modules/ember-cli/node_modules/babel-plugin-proto-to-assign/node_modules/lodash
- ember-cli node_modules/ember-cli
- abbrev@1.0.9 node_modules/ember-cli/node_modules/abbrev
- acorn@1.2.2 node_modules/ember-cli/node_modules/acorn
- after@0.8.1 node_modules/ember-cli/node_modules/after
- amdefine@1.0.0 node_modules/ember-cli/node_modules/amdefine
- ansi-escapes@1.4.0 node_modules/ember-cli/node_modules/ansi-escapes
- ansi-regex@2.0.0 node_modules/ember-cli/node_modules/ansi-regex
- ansi-styles@2.2.1 node_modules/ember-cli/node_modules/ansi-styles
- ansicolors@0.2.1 node_modules/ember-cli/node_modules/ansicolors
- aproba@1.0.4 node_modules/ember-cli/node_modules/aproba
- are-we-there-yet node_modules/ember-cli/node_modules/are-we-there-yet
- isarray@1.0.0 node_modules/ember-cli/node_modules/are-we-there-yet/node_modules/isarray
- array-equal@1.0.0 node_modules/ember-cli/node_modules/array-equal
- array-flatten@1.1.1 node_modules/ember-cli/node_modules/array-flatten
- array-to-error@1.1.1 node_modules/ember-cli/node_modules/array-to-error
- arraybuffer.slice@0.0.6 node_modules/ember-cli/node_modules/arraybuffer.slice
- asn1@0.2.3 node_modules/ember-cli/node_modules/asn1
- assert-plus@0.2.0 node_modules/ember-cli/node_modules/assert-plus
- ast-traverse@0.1.1 node_modules/ember-cli/node_modules/ast-traverse
- ast-types@0.8.12 node_modules/ember-cli/node_modules/ast-types
- async@1.5.2 node_modules/ember-cli/node_modules/async
- aws-sign2@0.6.0 node_modules/ember-cli/node_modules/aws-sign2
- aws4@1.4.1 node_modules/ember-cli/node_modules/aws4
- babel-core node_modules/ember-cli/node_modules/babel-core
- lodash@3.10.1 node_modules/ember-cli/node_modules/babel-core/node_modules/lodash
- babel-plugin-constant-folding@1.0.1 node_modules/ember-cli/node_modules/babel-plugin-constant-folding
- babel-plugin-dead-code-elimination@1.0.2 node_modules/ember-cli/node_modules/babel-plugin-dead-code-elimination
- babel-plugin-eval@1.0.1 node_modules/ember-cli/node_modules/babel-plugin-eval
- babel-plugin-inline-environment-variables@1.0.1 node_modules/ember-cli/node_modules/babel-plugin-inline-environment-variables
- babel-plugin-jscript@1.0.4 node_modules/ember-cli/node_modules/babel-plugin-jscript
- babel-plugin-member-expression-literals@1.0.1 node_modules/ember-cli/node_modules/babel-plugin-member-expression-literals
- babel-plugin-property-literals@1.0.1 node_modules/ember-cli/node_modules/babel-plugin-property-literals
- babel-plugin-proto-to-assign@1.0.4 node_modules/ember-cli/node_modules/babel-plugin-proto-to-assign
- babel-plugin-react-constant-elements@1.0.3 node_modules/ember-cli/node_modules/babel-plugin-react-constant-elements
- babel-plugin-react-display-name@1.0.3 node_modules/ember-cli/node_modules/babel-plugin-react-display-name
- babel-plugin-remove-console@1.0.1 node_modules/ember-cli/node_modules/babel-plugin-remove-console
- babel-plugin-remove-debugger@1.0.1 node_modules/ember-cli/node_modules/babel-plugin-remove-debugger
- babel-plugin-runtime@1.0.7 node_modules/ember-cli/node_modules/babel-plugin-runtime
Unfortunately both of these issues appear related to node/npm, and not directly to ember. Although I suspect reducing the number of dependencies (work in progress) will help, the underlying issue is not with ember-cli.
If you can share information that demonstrates the above to be false. Let me know.
@stefanpenner that's okay. Could you give me directions where to file these reports now?
node segfaulting during an npm
install may mean:
my system has 4GB memory out of which 3.7 is always available. Buggy build of node shouldn't be an issue here since every other app and package is working properly, unless there's something ember-cli is trying to do in a non-standard way. Also manually running npm install doesn't produces segmentation fault.
@agauniyal ember is merely delegating to npm for its install which appears to be running during the segfault.
segfault during this period unfortunately suggests something funky with something node or bellow. As ember-cli & npm, don't execute any native extensions.
I would recommend getting a coredump and reporting here feel free to cross link, as I am also quite curious.
I believe one can drop coredumps by setting ulimit -u unlimited
or something, and node will drop dumps on segfault.
https://github.com/ddopson/node-segfault-handler may be handy?
I've already spent much time on installing ember, if anyone wants to debug it he/she may install latest archlinux and node, npm packages. As I said this happens every time so it is entirely reproducible with current node and npm versions. If there's something like docker installation or alternative which exposes ports to interact with - something like homestead/valet and laravel, I could use ember. Tbh I'm looking into alternative frameworks for now.
Please see issue - https://github.com/ember-cli/ember-cli/issues/6255, this one is continuation of previous issue and the issue here - https://github.com/emberjs/ember.js/issues/14258