ruby-memory-issues

KO | EN

gitlite — search

#hacktoberfest #react #llm #go #rust #java #windows #kubernetes #vue #pytorch #security #openai #mcp #open-source

ruby-memory-issues

(★ 22)

🐲 Ruby Memory Issues and Where to Find Them

ruby-memory-issues Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Ruby Memory Issues and Where to Find Them [![Twitter Follow](https://img.shields.io/twitter/url/http/shields.io.svg?style=social&label=Follow)](https://twitter.com/stereobooster)

![](https://raw.githubusercontent.com/stereobooster/ruby-memory-issues/master/images/memory-bloat.svg)

## Memory Bloat

When code tries to allocate a lot of objects simultaneously.

**Where to find**: process big json or XML file in none streaming manner, or load a big number of objects from the database without batching.

**Symptoms**: "stepwise jumps" in memory.

![](https://raw.githubusercontent.com/stereobooster/ruby-memory-issues/master/images/memory-bloat.png)

---

![](https://raw.githubusercontent.com/stereobooster/ruby-memory-issues/master/images/memory-leak.svg)

## Ruby Leak

When reference to object lives longer than expected.

**Where to find**: caching, memoization, i18n.

**Examples**:
- http://blog.skylight.io/hunting-for-leaks-in-ruby/
- https://github.com/discourse/discourse/commit/830ce05fe64fd310d26d7da87ea6e4076696b7c8

**Symptoms**: constant grows in memory.

![](https://raw.githubusercontent.com/stereobooster/ruby-memory-issues/master/images/memory-leak.png)

Image credit: [samsaffron](https://samsaffron.com/archive/2015/03/31/debugging-memory-leaks-in-ruby).

## C Leak

When the leak happens in C-land.

**Examples**:
- http://www.be9.io/2015/09/21/memory-leak/
- https://github.com/ASoftCo/leaky-gems

---

![](https://raw.githubusercontent.com/stereobooster/ruby-memory-issues/master/images/object-grinder.svg)

## Object Grinder

This is not commonly recognized as a memory issue, but it is one. Happens when code uses a lot of temporary objects, which leads to increased pressure on GC and to memory fragmentation.

**Where to find**: everywhere.

**Examples**:
- default arguments https://github.com/JuanitoFatas/fast-ruby/pull/137
- string literals without freeze (`# frozen_string_literal: true`)

**Symptoms**: logarithm-like memory growth.

![](https://raw.githubusercontent.com/stereobooster/ruby-memory-issues/master/images/memory-fragmentation.png)

---

![](https://raw.githubusercontent.com/stereobooster/ruby-memory-issues/master/images/memory-hog.svg)

## Memory Hog

Not commonly recognized as a memory issue, but it is one. Happens when code loads big sets of data and never unloads them.

**Where to find**: data gems.

**Examples**:
- https://github.com/mime-types/ruby-mime-types/issues/123
- https://github.com/RubyMoney/money/pull/691
- https://github.com/rack/rack-contrib/pull/131
- https://github.com/svenfuchs/i18n/pull/391

ruby-memory-issues

ruby-memory-issues Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

ruby-memory-issues

ruby-memory-issues Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README