Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

Heroku review apps: memory issue #322

Closed
Matt-Butler opened this issue May 5, 2017 · 5 comments · Fixed by #326
Closed

Heroku review apps: memory issue #322

Matt-Butler opened this issue May 5, 2017 · 5 comments · Fixed by #326
Assignees

Comments

@Matt-Butler
Copy link
Contributor

Matt-Butler commented May 5, 2017

When loading the review apps, we see this page:
screen shot 2017-05-05 at 4 41 21 pm

This is due to the webpack-dev-server taking up too much memory.

@Matt-Butler
Copy link
Contributor Author

We might want to create the static assets and host them on heroku to get around the memory issue.

@windse7en
Copy link
Contributor

Heroku Error R14(Memory quota exceeded): https://gist.github.com/windse7en/e9685f48af1b015ff1245c68297985bc

@windse7en
Copy link
Contributor

windse7en commented May 8, 2017

Heroku logs after updating express: https://gist.github.com/windse7en/b5b0df051286df8970a83c0f3ebfc4e3

After using built assets and express server, we get rid of most of the R14 error. But there are still some R14 errors. That dues to the webpack compile process taking too much memory.

@windse7en
Copy link
Contributor

In the #326, move the build process into heroku postbuild. It will run for any new commit and won't have the memory issue in the build process. All the build logs information can be found in the Heroku dashboard.

@windse7en
Copy link
Contributor

Close this memory issue. As we move the build process into the heroku build time, there is no memory issue in the logs.

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

Successfully merging a pull request may close this issue.

2 participants