Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

next dev fails randomly on CI since 9.3.5 - exit code 137

See original GitHub issue

Bug report

Describe the bug

Since upgrading to 9.3.5, next dev has failed with exit code 137 during our CircleCI builds about 20% of the time.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

Update to 9.3.5
Run next dev on CircleCI
???
No profit 😞

Expected behavior

It would be nice if it didn’t do this.

Screenshots

> hi-next@0.3.1 dev /root/repo
> next dev

[ wait ]  starting the development server ...
[ info ]  waiting on ********************* ...
> Using external babel configuration
> Location: "/root/repo/babel.config.js"
[ ready ] compiled successfully - ready on *********************
[ wait ]  compiling ...
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

[ ready ] compiled successfully - ready on *********************
Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! hi-next@0.3.1 dev: `next dev`
npm ERR! Exit status 137
npm ERR! 
npm ERR! Failed at the hi-next@0.3.1 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!     /root/.npm/_logs/2020-04-16T19_20_50_059Z-debug.log


Exited with code exit status 137
CircleCI received exit code 137

System information

OS: Debian (cypress/base:12.14.0) More info here
Browser (if applies) [e.g. chrome, safari]
Version of Next.js: 9.3.5
Version of Node.js: 12.14.0

Additional Info

I haven’t seen this at all when running locally.

Issue Analytics

State:
Created 3 years ago
Comments:7 (6 by maintainers)

Top GitHub Comments

3reactions

Timercommented, Sep 10, 2020

Closing as there was no reproduction given. Feel free to investigate this!

1reaction

manhcuongincusar1commented, Aug 2, 2021

This 137 node happens when runs out of memory, almost vps with 1gb ram may get this issues. So you can create virtual ram for your VPS with “swap” on Linux. check it out here: https://linuxize.com/post/how-to-add-swap-space-on-ubuntu-20-04/