Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Using iojs-v3.2.0 throws an error: 'Segmentation fault: 11' when running 'npm start' #2455

Closed
license2e opened this issue Aug 27, 2015 · 5 comments
Closed

Using iojs-v3.2.0 throws an error: 'Segmentation fault: 11' when running 'npm start' #2455

license2e opened this issue Aug 27, 2015 · 5 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@license2e
Copy link 

$ npm start

> <App>@0.0.1 start /path/to/<App>
> node_modules/react-native/packager/packager.sh

node_modules/react-native/packager/packager.sh: line 19: 11819 Segmentation fault: 11  node "$THIS_DIR/packager.js" "$@"

npm ERR! Darwin 14.5.0
npm ERR! argv "/Users/<user>/.nvm/versions/io.js/v3.2.0/bin/iojs" "/Users/<user>/.nvm/versions/io.js/v3.2.0/bin/npm" "start"
npm ERR! node v3.2.0
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE
npm ERR! <App>@0.0.1 start: `node_modules/react-native/packager/packager.sh`
npm ERR! Exit status 139
npm ERR!
npm ERR! Failed at the <App>@0.0.1 start script 'node_modules/react-native/packager/packager.sh'.
npm ERR! This is most likely a problem with the <App> package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node_modules/react-native/packager/packager.sh
npm ERR! You can get their info via:
npm ERR!     npm owner ls <App>
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /path/to/<App>/npm-debug.log

npm-debug.log: https://gist.github.com/license2e/7583a974f8112c8945f0

Note: To solve the issue, I reverted back to ios-v2.0.0 (sorry, I didn't have time to test any others at this time..)
@ide
Copy link
Contributor

ide commented Aug 27, 2015

io.js 3 is not yet supported but will probably be in 0.12. Getting ready for Node 4!

@ide ide mentioned this issue Aug 27, 2015
Merged
sahrens pushed a commit to sahrens/react-native that referenced this issue Sep 3, 2015
@ide
[npm] Update to stacktrace-parser@0.1.3 and ws@0.8.0 to satisfy io.js…

Verified

This commit was signed with the committer’s verified signature.
marco-ippolito Marco Ippolito
GPG key ID: 27F5E38D5B0A215F
Verified
Learn about vigilant mode
7f65971 
… 3 / Node 4

Summary:
The previous version of stacktrace-parser 0.1.2 had an line in its package.json file that required Node <= 2.x. That line was removed, so it no longer warns on io.js 3.x or Node 4.x.

Similarly, ws 0.8.0 was published with support for the new V8, so it compiles with io.js 3.x and therefore should work with Node 4.x.

Updated the Travis file as well to run on io.js 3.x.

Fixes facebook#2258, facebook#2455

Closes facebook#2398
Github Author: James Ide <ide@jameside.com>
ide added a commit that referenced this issue Sep 8, 2015
@ide
[npm] Update to stacktrace-parser@0.1.3 and ws@0.8.0 to satisfy io.js…

Verified

This commit was signed with the committer’s verified signature.
marco-ippolito Marco Ippolito
GPG key ID: 27F5E38D5B0A215F
Verified
Learn about vigilant mode
2d8ec5e 
… 3 / Node 4

Summary:
The previous version of stacktrace-parser 0.1.2 had an line in its package.json file that required Node <= 2.x. That line was removed, so it no longer warns on io.js 3.x or Node 4.x.

Similarly, ws 0.8.0 was published with support for the new V8, so it compiles with io.js 3.x and therefore should work with Node 4.x.

Updated the Travis file as well to run on io.js 3.x.

Fixes #2258, #2455

Closes #2398
Github Author: James Ide <ide@jameside.com>
@browniefed
Copy link
Contributor

@brentvatne this seems fixed with some updated deps, and also master supports node 4. Close.

@browniefed
Copy link
Contributor

@ide this is a node issue, probably close it.

@ide
Copy link
Contributor

ide commented Sep 13, 2015

@license2e when you change Node versions be sure to clean out your node_modules and rebuild.

@ide ide closed this as completed Sep 13, 2015
@soxunyi
Copy link

soxunyi commented Sep 17, 2015

Yes, you should clean out your node_modules and rebuild. You can run 'npm rebuild' on your terminal. Please try.

@facebook facebook locked as resolved and limited conversation to collaborators Jul 21, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 21, 2018
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Assignees
No one assigned
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@ide @browniefed @soxunyi @license2e @react-native-bot