# Investigating a Ruby Memory Leak in the HEY App

DevFeed: [Investigating a Ruby Memory Leak in the HEY App](<https://devfeed.tech/articles/my-adventures-hunting-down-a-ruby-memory-leak-33495.md>)

Original publisher: [Read original article](<https://dev.37signals.com/adventures-hunting-down-ruby-memory-leak/>)

Author: Jacopo Beschi

Published: 2024-03-07T18:00:00Z

Content type: tutorial

Language: en

Sources: [37signals Dev](<https://devfeed.tech/sources/37signals-dev.md>)

Topics: [Memory Leaks](<https://devfeed.tech/topics/memory-leaks.md>), [Ruby](<https://devfeed.tech/topics/ruby.md>), [App](<https://devfeed.tech/topics/app.md>), [Server](<https://devfeed.tech/topics/server.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [gc](<https://devfeed.tech/tags/gc.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [memory-leak](<https://devfeed.tech/tags/memory-leak.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [trace](<https://devfeed.tech/tags/trace.md>)

## AI overview

This article describes how a team investigated a slow Ruby memory leak in the HEY app. It covers analyzing Ruby heap allocation statistics, extracting heap dumps with rbtrace, enabling object allocation tracing, and comparing dumps over time while limiting the diagnostic impact to one app host.

## Source excerpt

What I learned on the journey chasing a tricky memory leak in HEY.