In my last post, we looked at how you can dig into memory "leaks" on Heroku. These techniques all work well if you can reproduce the memory bloat locally. When you can't, we can take a "heap dump" off of a running production server and analyze it for more information. In this two-post series, we'll look at the basics of what a heap dump is, what the contents look like, how to analyze one, and how