You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We definitely have a memory leak, primarily in puma. 1 GB in 4 days.
For development the simplest thing would be a cron job to restart it. For a true production system I’d try to figure out what’s going on. I don’t know whether there are tools
If you look for “ruby memory leak” you’ll see various techniques. It looks like you really want ruby 2.1. If it becomes important to do this debugging I’d see whether the application can run on 2.1.
The text was updated successfully, but these errors were encountered:
jkim-ru
changed the title
Memory Leak that kills rails application due to "out of memory"
[Bug] Memory Leak that kills rails application due to "out of memory"
Oct 9, 2017
From Chuck:
We definitely have a memory leak, primarily in puma. 1 GB in 4 days.
For development the simplest thing would be a cron job to restart it. For a true production system I’d try to figure out what’s going on. I don’t know whether there are tools
If you look for “ruby memory leak” you’ll see various techniques. It looks like you really want ruby 2.1. If it becomes important to do this debugging I’d see whether the application can run on 2.1.
The text was updated successfully, but these errors were encountered: