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

[BUG] Segmentation fault on npm install (errors about different packages) #986

Closed
vitaly-zdanevich opened this issue Mar 6, 2020 · 6 comments
Labels
Bug thing that needs fixing

Comments

@vitaly-zdanevich
Copy link

vitaly-zdanevich commented Mar 6, 2020

After my colleague added to package.json "material-design-icons": "^3.0.1":

{
  "name": "happy-marketer",
  "version": "0.1.0",
  "private": true,
  "homepage": "https://happy-marketer.gms-ai.com/",
  "dependencies": {
    "@testing-library/jest-dom": "^4.2.4",
    "@testing-library/react": "^9.4.0",
    "@testing-library/user-event": "^7.2.1",
    "lodash": "^4.17.15",
    "material-design-icons": "^3.0.1",
    "react": "^16.12.0",
    "react-dom": "^16.12.0",
    "react-router-dom": "^5.1.2",
    "react-scripts": "3.3.0"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  }
}

I tried to npm cache verify:

Cache verified and compressed (~/.npm/_cacache):
Content verified: 3017 (74101030 bytes)
Content garbage-collected: 167 (16073226 bytes)
Index entries: 4611
Finished in 119.14s

But npm install again return Segmentation fault.

Also I tried
npm cache clean --force

npm install --verbose:

npm info it worked if it ends with ok
npm verb cli [ '/usr/bin/node', '/usr/bin/npm', 'install', '--verbose' ]
npm info using npm@6.13.4
npm info using node@v12.14.0
npm verb npm-session be7d50e65d2d8346
npm info lifecycle happy-marketer@0.1.0~preinstall: happy-marketer@0.1.0
npm timing stage:loadCurrentTree Completed in 21ms
npm timing stage:loadIdealTree:cloneCurrentTree Completed in 1ms
npm timing stage:loadIdealTree:loadShrinkwrap Completed in 2399ms
npm http fetch GET 200 https://registry.npmjs.org/material-design-icons 45ms (from cache)
Segmentation fault.] | fetchMetadata: http fetch GET 200 https://registry.npmjs.org/material-design-icons 45ms (from c

node --version:
v12.14.0

npm --version:
6.13.4

OS: Linux Gentoo i686 with all current updates. My make.conf:

COMMON_FLAGS="-O2 -march=athlon64 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"

# Output from cpuid2cpuflags
CPU_FLAGS_X86="3dnow 3dnowext mmx mmxext popcnt sse sse2 sse3 sse4a"

# NOTE: This stage was built with the bindist Use flag enabled
PORTDIR="/var/db/repos/gentoo"
DISTDIR="/var/cache/distfiles"
PKGDIR="/var/cache/binpkgs"

# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C

USE="-qt5 -dvdr -bluetooth alsa -pulseaudio minizip -closure-compile -cups -gnome-keyring -kerberos -proprietary-codecs icu system-icu inspector wayland gles"

# https://wiki.gentoo.org/wiki/Radeon
VIDEO_CARDS="radeon r600

net-libs/nodejs is installed with default build flags.

I have enough of RAM.

Also tried to close browser.

Also tried npm install through the tty.

Also tried to install after computer reboot.

Tried to remove package-lock.json

Tried to remove "material-design-icons": "^3.0.1" from package.json: now npm install works correctly.

Tried on another machine with Gentoo i686: also segmentation fault.

@DanielRuf
Copy link

Tried to remove "material-design-icons": "^3.0.1" from package.json: now npm install works correctly.

Tried on another machine with Gentoo i686: also segmentation fault.

Isn't this an issue with the package then?

@vitaly-zdanevich
Copy link
Author

Maybe...

@vitaly-zdanevich
Copy link
Author

vitaly-zdanevich commented May 12, 2020

Now I have changed package.json:

{
  "name": "happy-marketer",
  "version": "0.1.0",
  "private": true,
  "homepage": "https://happy-marketer.gms-ai.com/",
  "dependencies": {
    "@testing-library/jest-dom": "^4.2.4",
    "@testing-library/react": "^9.4.0",
    "@testing-library/user-event": "^7.2.1",
    "@types/jest": "^25.2.1",
    "@types/lodash": "^4.14.149",
    "@types/node": "^13.11.1",
    "@types/react": "^16.9.34",
    "@types/react-dom": "^16.9.6",
    "lodash": "^4.17.15",
    "react": "^16.12.0",
    "react-dom": "^16.12.0",
    "react-router-dom": "^5.1.2",
    "react-scripts": "^3.4.0",
    "react-select": "^3.0.8",
    "typescript": "^3.8.3"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  }
}

And I cannot npm install without Segmentation fault.

Sometimes I get this message:

Segmentation fault.] / extract:rimraf: sill extract rimraf@2.7.1 extracted to /home/vitaly/global-marketing-solutions/

Sometimes:

Segmentation fault.] - extract:jest: sill tarball no local data for jsdom@11.12.0. Extracting by manifest.

Also:

Segmentation fault.] - extract:@csstools/convert-colors: sill tarball no local data for minipass-collect@1.0.2. Extrac

@vitaly-zdanevich vitaly-zdanevich changed the title [BUG] Segmentation fault on npm install (on material-design-icons) [BUG] Segmentation fault on npm install (errors about different packages) May 12, 2020
@narkhedek3
Copy link

Hi @vitaly-zdanevich,
I am also facing the same issue. npm install is returning segmentation fault.
have you found any solution to resolve this issue?

@vitaly-zdanevich
Copy link
Author

As I remember I changed a package version or removed some dependencies.

@darcyclarke darcyclarke added the Bug thing that needs fixing label Oct 30, 2020
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Bug thing that needs fixing
Projects
None yet
Development

No branches or pull requests

4 participants