We had good success with tracking down heroku memory leaks with Oink on a Rails4 ruby2.0 application. It turned out to be about 30% the code, 70% the defaults f

We had good success with tracking down heroku memory leaks with Oink on a Rails4 ruby2.0 application. It turned out to be about 30% the code, 70% the defaults for the ruby2.0 garbage collector. Tweaking the default GC settings helped with most of our problem.