-
-
Notifications
You must be signed in to change notification settings - Fork 36.1k
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
Comments
An luck tracking this down? |
Going to close this for now. Hopefully this is related to error handling that is slowly being closed up.. |
Re opening. Just saw a memory error in the logs. |
@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!) |
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. |
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). |
ISSUES CLOSED: freeCodeCamp#206
Looking through Heroku logs we are getting a lot of R14 Memory errors.
The text was updated successfully, but these errors were encountered: