Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Error upgrading to v0.9.1: Segmentation fault (core dumped) #52

Closed
nimarion opened this issue Nov 13, 2021 · 2 comments
Closed

Error upgrading to v0.9.1: Segmentation fault (core dumped) #52

nimarion opened this issue Nov 13, 2021 · 2 comments

Comments

@nimarion
Copy link

nimarion commented Nov 13, 2021

I get this error when calling the ipx endpoint using version 0.9.1 together with the nuxtjs image module as a custom middleware . 0.8.0 worked fine without any problems.

Segmentation fault (core dumped)
npm ERR! code ELIFECYCLE
npm ERR! errno 139
npm ERR! lcr@ dev: `nuxt`
npm ERR! Exit status 139
npm ERR! 
npm ERR! Failed at the lcr@ dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/niklas/.npm/_logs/2021-11-13T13_51_21_220Z-debug.log

debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev' ]
2 info using npm@6.14.15
3 info using node@v14.18.1
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle lcr@~predev: lcr@
6 info lifecycle lcr@~dev: lcr@
7 verbose lifecycle lcr@~dev: unsafe-perm in lifecycle true
8 verbose lifecycle lcr@~dev: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/niklas/code/www/node_modules/.bin:/home/niklas/.sdkman/candidates/maven/current/bin:/home/niklas/.sdkman/candidates/java/current/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/niklas/.bin:/home/niklas/.bin
9 verbose lifecycle lcr@~dev: CWD: /home/niklas/code/www
10 silly lifecycle lcr@~dev: Args: [ '-c', 'nuxt' ]
11 silly lifecycle lcr@~dev: Returned: code: 139  signal: null
12 info lifecycle lcr@~dev: Failed to exec dev script
13 verbose stack Error: lcr@ dev: `nuxt`
13 verbose stack Exit status 139
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:400:28)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:400:28)
13 verbose stack     at maybeClose (internal/child_process.js:1058:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
14 verbose pkgid lcr@
15 verbose cwd /home/niklas/code/www
16 verbose Linux 5.8.0-63-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "dev"
18 verbose node v14.18.1
19 verbose npm  v6.14.15
20 error code ELIFECYCLE
21 error errno 139
22 error lcr@ dev: `nuxt`
22 error Exit status 139
23 error Failed at the lcr@ dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 139, true ]
@ThornWalli
Copy link
Contributor

Bring the problem to topic here #60

@pi0
Copy link
Member

pi0 commented Jun 20, 2022

I hope this issue will be solved with the next release of IPX and updated node-fetch dependency. If not, a reproduction would be nice 🙏🏼

@pi0 pi0 closed this as completed Jun 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants