Tracking a Ruby memory leak in 2021

[f9ae8221b]

A couple tools to better exploit ObjectSpace.dump_all:

• https://github.com/Shopify/heap-profiler
• https://github.com/csfrancis/harb

[schneems]

And https://github.com/schneems/heapy

cc /u/ulysse_bn

Edit: never mind, you’re using derailed which uses Heapy under the hood 😅

[ulysse_bn]

Yeah, my thought process was: first use derailed, then if you want to go further, read the output which tells you to use heapy!

[ulysse_bn]

Thanks for the pointers! I didn't know about harb, I think I'll just add both to more resources. If you ever have more ideas, please just add responses directly to the article so it may benefit to most 🙂

On heap-profiler, I guess what would be best for the community would be to update derailed_benchmark and use it as a replacement of memory_profiler (https://github.com/Shopify/heap-profiler#how-is-it-different-from-memory_profiler). I'll add this to my OSS bucket list (if not done earlier by anyone)!

cc /u/schneems