Is growing memory usage always a memory leak?

Steady, continuous growth over a session is the signature of a leak, so usually yes. A stable game holds roughly steady memory once loaded; one whose memory climbs the longer it runs has something accumulating without being freed. This is distinct from a one-time spike (a sudden jump when loading a big level, which may come back down). If memory grows continuously and unbounded over time, that's a leak, and tracing what keeps accumulating points at the cause.

How do I find what's causing memory to grow in my game?

Recognize the growth-over-time signature, then trace what keeps accumulating: the usual suspects are objects never removed from collections, event handlers never unsubscribed, unbounded caches, and assets never unloaded. Capturing memory behavior over real, longer sessions reveals the climb (which quick tests miss), and field data showing which sessions and situations correlate with memory pressure narrows down where the leak is, so you can find and fix the specific pattern that's not freeing memory.

What Causes Memory Usage to Grow Over Time?

Q: What causes memory usage to grow over time?

Memory usage that grows continuously over a session is almost always a memory leak, memory allocated and never freed, accumulating. The causes are objects added to collections and never removed, event subscriptions or callbacks never cancelled (keeping objects alive forever), caches that only grow, assets loaded but never unloaded (especially reloading on area entry), and references that outlive their use. Each leaves memory nothing will free, so it piles up until the game slows or crashes.

Quick answer: Memory usage that grows over a session is almost always a memory leak: memory allocated and never freed. From objects kept in collections, handlers never unsubscribed, unbounded caches, and assets never unloaded.

If your game's memory usage climbs the longer it runs, that steady growth is a specific and recognizable problem, a memory leak. Here's what causes memory usage to grow over time and how to recognize it.

Growth Over Time Means a Leak

A stable game holds roughly steady memory; one whose memory climbs continuously over a session has a leak, memory allocated and never released, accumulating. The causes are the classic leak patterns.

Objects added to a collection and never removed, a list or dictionary that only grows
Event subscriptions or callbacks never cancelled, listeners that keep objects alive forever
Caches that only grow, cached data never evicted or bounded
Assets loaded but never unloaded, especially reloading on each area entry without freeing
References that outlive their use, holding onto something that should have been freed

Each leaves memory nothing will free, so it piles up. Steady, continuous growth over a session is the signature distinguishing a leak from a one-time spike.

Why It Only Shows Up Over Time

A leak's growth is gradual, so it doesn't appear in quick tests, you have to play for a while before the accumulation becomes visible and causes problems. This is why leaks escape testing and only crash players in long sessions, when memory finally exceeds the limit.

Bugnet captures memory-related crashes and performance over real sessions, so the long-session out-of-memory crashes a leak causes surface in your data even though a quick test would miss them. Recognizing the growth-over-time pattern is how you identify a leak.

Finding What's Growing

Finding the leak means tracing what keeps accumulating, the suspects are growing collections, uncancelled handlers, unbounded caches, and unloaded assets. Field data showing which longer sessions correlate with memory pressure narrows where the growth is happening.

Bugnet helps you see which situations and longer sessions correlate with memory pressure and crashes, pointing you toward the leak. So memory usage growing over time is caused by a leak, and finding it means recognizing the growth signature and tracing what accumulates without being freed.

Memory growing over a session is almost always a leak, memory never freed, from objects kept in collections, uncancelled handlers, unbounded caches, or unloaded assets. The growth signature only shows in longer sessions.