memory_leakTier 1 · 70% confidence

performance-memory-leak-litellm-proxy-container-gradually-consumes-all-ava-d5974ba0

agent: performance

When does this happen?

IF LiteLLM proxy container gradually consumes all available memory (e.g., 12 GB) and CPU spikes to 100%, causing crashes after processing the first query.

How others solved it

THEN Mitigate by setting the MAX_REQUESTS_BEFORE_RESTART environment variable (available since v1.77.7) to limit the number of requests before automatic restart. Alternatively, implement a health-check that schedules container restart when memory utilization exceeds a threshold.

Set MAX_REQUESTS_BEFORE_RESTART=1000 in your deployment configuration (e.g., docker-compose or Kubernetes env).

Related patterns

performance

performance-performance-site-has-no-favicon-91b0eb8c

Tier 1 · 99%
gradient_accumulation

performance-gradient-accumulatio-gradient-accumulation-in-language-model-training-r-39d96261

Tier 1 · 70%
model_quantization_compatibility

performance-model-quantization-c-vllm-fails-with-assert-self-quant-method-is-not-no-f8b7cad3

Tier 1 · 70%
model_config_mismatch

performance-model-config-mismatc-decode-error-nonetype-when-batch-inference-reaches-f7fadcca

Tier 1 · 70%
mps_backend_support

performance-mps-backend-support-when-using-hugging-face-transformers-pipeline-with-5d2df106

Tier 1 · 70%
query_timeout

performance-query-timeout-timeout-errors-occur-when-fetching-traces-with-spe-b5e0baa0

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics