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

Possible Memory Leak #206

Closed
terakilobyte opened this issue Mar 15, 2015 · 6 comments
Closed

Possible Memory Leak #206

terakilobyte opened this issue Mar 15, 2015 · 6 comments
Labels
type: bug Issues that need priority attention. Platform, Curriculum tests (if broken completely), etc.

Comments

@terakilobyte
Copy link
Contributor

Looking through Heroku logs we are getting a lot of R14 Memory errors.

@terakilobyte terakilobyte added type: bug Issues that need priority attention. Platform, Curriculum tests (if broken completely), etc. in progress labels Mar 15, 2015
@BerkeleyTrue
Copy link
Contributor

An luck tracking this down?

@BerkeleyTrue
Copy link
Contributor

Going to close this for now. Hopefully this is related to error handling that is slowly being closed up..

@BerkeleyTrue
Copy link
Contributor

Re opening. Just saw a memory error in the logs.

@QuincyLarson
Copy link
Contributor

@terakilobyte @BerkeleyTrue We need to try your strong loop tool so we can isolate this. This is contingent on us spinning up a duplicate environment to play with (production shouldn't be touched!)

@terakilobyte
Copy link
Contributor Author

The duplicate environment will take minutes to set up. I've further isolated the memory leak to revolve around the courseware, bonfire, and field-guide controllers.

@QuincyLarson
Copy link
Contributor

This doesn't actually seem to be a memory leak, as it plateaus at around 800mb of ram usage. We think this is just how much ram our app needs once all our challenges are cached (hence the gradual increase up to 800mb).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Issues that need priority attention. Platform, Curriculum tests (if broken completely), etc.
Projects
None yet
Development

No branches or pull requests

3 participants