Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix [Bug]: Heavy RAM usage over some time

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fix / Workaround

v1.83.14-stable.patch.3

RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

After some time, from some reason LiteLLM will reach maximum of the RAM capacity for the pods on Kubernetes and application pod will crash eventually. We do not understand what is causing this kind of issue with the memory leaks but it is happening. We as firm saw earlier that users were reporting similar issue and developer were claiming that they fixed the issue but, issue is repeating. LiteLLM application is being run on the two pod configuration in separated namespace. Application has attached Redis as caching service but even with that we are facing an issues. Application has request and limit of 4GB which is more then enough for this kind of application.

<img width="901" height="267" alt="Image" src="https://github.com/user-attachments/assets/3475ea9c-98d8-432c-914e-9316537b9a7e" />

Steps to Reproduce

  1. Deploy LiteLLM on Kubernetes
  2. After day or two, pod memory will be filled (4GB) and eventually application will crash and restart

Relevant log output

What part of LiteLLM is this about?

Proxy

What LiteLLM version are you on ?

v1.83.14-stable.patch.3

Twitter / LinkedIn details

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#retrieval issue#search optimization#API routing#API middleware#memory leak

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix [Bug]: Heavy RAM usage over some time