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 Command failed with exit code 137 #1177

Closed
mashirozx opened this issue Dec 2, 2017 · 10 comments
Closed

error Command failed with exit code 137 #1177

mashirozx opened this issue Dec 2, 2017 · 10 comments

Comments

@mashirozx
Copy link

Here when install it, it shows:

root@mine:/var/www/node/stackedit# yarn install
yarn install v1.3.2
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
$ gulp build-prism
[23:22:21] Using gulpfile /var/www/node/stackedit/gulpfile.js
[23:22:21] Starting 'build-prism'...
[23:22:21] Finished 'build-prism' after 114 ms
Done in 1.65s.
root@mine:/var/www/node/stackedit# yarn start

yarn run v1.3.2
$ node build/dev-server.js
> Starting dev server...
Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

On Ubuntu 17.04, with: nodejs v8.9.1; yarn 1.3.2; npm 5.5.1

Sorry, I'm new to Node, and the official site had a bad connection in my country, so I need to install StackEdit locally... Thanks,

@mashirozx
Copy link
Author

P.S. Someone said it's caused by the memory limit of the machine :(
Is that true? My server has 1G RAM, is it enough? 😢

@benweet
Copy link
Owner

benweet commented Dec 21, 2017

That’s right, this is provoked by linux’s oom killer. Try to increase the ram or the swap.

@benweet benweet closed this as completed Dec 21, 2017
@thinsoldier
Copy link

thinsoldier commented Sep 21, 2018

How much should it be increased to if 1GB is not enough?

@mashirozx
Copy link
Author

@thinsoldier I tried a 4 GB machine, still not enough :-/

@thinsoldier
Copy link

thinsoldier commented Sep 22, 2018

@mashirozx I encountered the error while running the new vue-ui which uses some kind of server to serve its gui and then webpack dev server to serve my project.

At 512 megs the dev server failed to start, even with the vue-ui gui turned off.

With yarn instead of npm at 512 megs both servers started but if I navigated within the vue-ui gui site the dev server would crash.

At 1GB I would see errors mentioning memory in the terminal of the dev server but it wouldn't crash.

It seems that 2gb is enough for me but I think the switch from npm to yarn might have something to do with it.

@deXterbed
Copy link

Thanks guys, i needed to increase the swap size!

@phillips-tech
Copy link

I got this when compiling an Angular 5 app, just changed the memory on my Docker settings to 2GB and that did the trick.

@Frank-686
Copy link

我虚拟机给了8G内存 还是会报错 请问有解决方案嘛

@omeryousaf
Copy link

omeryousaf commented Jul 15, 2021

I got this when compiling an Angular 5 app, just changed the memory on my Docker settings to 2GB and that did the trick.

Had a similar issue on Mac while running a unit testing job for an Angular 4 app (with karma as test framework), i had to increase the space allocation for a VirtualBox (one of the tools through which docker is orchestrated on a mac) instance from 1024MB storage limit to 2048MB. I followed the way described in https://stackoverflow.com/a/36982696/4997994.

@LeulAria
Copy link

LeulAria commented May 8, 2023

check your ram if it's used by other things
htop or another tool and kill unused processes

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

8 participants