Skip to content

[$50] Heroku memory quota #15

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

Closed
gondzo opened this issue Dec 28, 2016 · 8 comments
Closed

[$50] Heroku memory quota #15

gondzo opened this issue Dec 28, 2016 · 8 comments
Assignees

Comments

@gondzo
Copy link
Contributor

gondzo commented Dec 28, 2016

Heroku logs show frequent restarts due to

Process running mem=530M(103.6%)8:13 PM
Error R14 (Memory quota exceeded)

Running the process locally requires < 100MB

@chqy24
Copy link
Collaborator

chqy24 commented Dec 28, 2016

I will take this one, how can I assign it to myself?
handle: ouyangki

@chqy24
Copy link
Collaborator

chqy24 commented Dec 28, 2016

I've already limit the memory to 512M in previous challenge, and I will try to reproduce this memory overflow issue.

@chqy24
Copy link
Collaborator

chqy24 commented Dec 28, 2016

@gondzo, can you provider more info about the issue, which branch and all the environment variable value

@gondzo
Copy link
Contributor Author

gondzo commented Dec 28, 2016

@chqy24
both dev and master branch, environment is the same as in .env.example

@chqy24
Copy link
Collaborator

chqy24 commented Dec 28, 2016

@gondzo, in the script of "heroku:dev:init", I set a environment variable NODE_ENV=development, which will enable hot module update for local develop, in fact this might be useless in a heroku app.
How do you think if I disable that 'hot module update' feature in dev of heroku by setting NODE_ENV to another value like 'dev'?

@gondzo
Copy link
Contributor Author

gondzo commented Dec 28, 2016

Yes, disabling hot module replacement is ok. You can even change it to production as that's what makes most sense for a heroku app

@chqy24
Copy link
Collaborator

chqy24 commented Dec 28, 2016

Although I think this issue is caused by that 'hot module update' feature, I also reduce the limitation for both of 'npm run build' and 'npm run start' to 384M, you can adjust the value in 'package.json' according to your need. FYI, a limitation of 256M for 'npm run build' will be failed according to my test.

I already create a PR here

@kbowerma
Copy link
Contributor

kbowerma commented Feb 1, 2017

payment record created DRONESERIES-8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants