PricingPricingDocsDocsBlogBlogBook a demoBook a demoCompanyCompany (opens in a new tab)
Product
DocsAPI ReferencePricingConsole DemoBlogCompany
Start Freev3.4.7
Wave Diagnosis

Memory Leak Detection

Watches the hourly minimum memory of each container and flags a floor that keeps rising, so you can act before the container is OOMKilled.

The challenge

Memory grows 50 MB a day, and Kubernetes says nothing until OOMKilled

kubernetes.io, Assign Memory Resources to Containers and Pods, and Resource Management for Pods and Containers. The 50 MB a day is illustrative, from an example in the Wave Memory Leak Detection docs.

A container that allocates more memory than its limit "becomes a candidate for termination", and the kernel enforces memory limits with OOM kills (kubernetes.io). Until that moment, the Pod stays Running, and nothing in its status warns about the rising memory.

A slow leak hides inside the normal sawtooth. Each garbage collection frees memory, but the low point of each cycle keeps rising, a little every day.

Memory rises until OOMKilled, then a rising floor flagged earlyWithout WaveWith WaveOOMKilled on day 6flagged on day 3
Without Wave
Memory rises 50 MB a day until the container is OOMKilledmemory usememory limitOOMKilledday 0day 2day 4day 6
Memory climbs and drops with each garbage collection, but the low point rises about 50 MB a day. The Pod stays Running until the peak reaches the limit on day 6, and the container is OOMKilled.
With Wave
Wave flags the rising floor as Steady Growth on day 3memory usehourly minimummemory limitSteady Growthflagged on day 3day 0day 2day 4day 6
Wave draws the hourly minimum, the orange line. The rising floor is flagged as Steady Growth on day 3, while the container still has room below its limit.

OOM kill at the memory limit: kubernetes.io. Hourly minimum and Steady Growth: Wave Memory Leak Detection docs. The curve, 50 MB a day, the limit, and the days are illustrative.

How Wave does it

From a rising memory floor to OOMKilled
Kubernetes by defaultSeen after the crash
  1. Container
    memory goes past its limit
  2. ↓over limit→
    Linux kernel
    enforces the limit with an OOM kill
  3. ↓OOM kill→
    kubelet
    restarts the container with a back-off
  4. ↓status→
    kubectl describe pod
    shows OOMKilled after the crash
Wave DiagnosisRising floor flagged while the Pod runs
  1. Wave Agent
    memory per container, with cAdvisor
  2. ↓gRPC→
    Wave Core
    keeps the hourly minimum, up to about 5 days
  3. ↓hourly floor→
    Leak patterns
    Steady Growth or Trend Based Growth, with a confidence score
  4. ↓flagged→
    Wave Console
    a leak tab and an OOM risk tab
Default lane: kubernetes.io (Assign Memory Resources, Resource Management for Pods and Containers, Pod Lifecycle). Wave lane: Wave Memory Leak Detection docs and Wave Architecture docs.
1

Watch the floor

Wave tracks the hourly minimum memory of each container, over up to about 5 days. Normal use moves up and down; a leak keeps raising that floor.

2

Name the pattern

Each detection is Steady Growth or Trend Based Growth, with the baseline memory, the recent memory, the increase, and a confidence score. A bubble chart puts the leaks that are both fast and large in one corner.

3

Check the limit too

The Possible OOM Risk tab lists workloads running close to their memory limit now, leak or not. You set what counts as close in OOM Risk Settings.

Related in Wave Diagnosis

Pod / Container Failures →Pod Scheduling Delay Detection →CPU Utilization Analysis →Idle Node Detection →Unused PV Detection →Cluster Resource Forecast →PV Capacity Forecast →Read the docs →
Book a demoStart free
Product
Wave GPUAI Infrastructure Professional ServiceWaveWave AI Agent2026 Q4
Resources
DocsAPI ReferenceBlogConsole DemoPricing
Company
STCLabBook a demoContact
STCLab© 2026 Wave All rights reserved.
Terms of ServicePrivacy PolicyCookies