[Bug]: The Logs page from the UI console has crashed after filtering a session_id

[oscarooi-bt]

What happened?

While navigating to the Logs page from the console and clicked on a session_id from a log item as shown below, no entries were displayed initially.

After around 50-60 seconds, the Logs page has crashed with browser error code "out of memory".

Browser: Google Chrome
Constantly reproducible: Yes from MacOS and Windows machines.

Remark: The specific session_id which I was navigating from the Logs page is expected to list of a large number of items based on the selected session_id.

Relevant log output

Are you a ML Ops Team?

No

What LiteLLM version are you on ?

v1.74.3-stable.patch.4

Twitter / LinkedIn details

No response

[ishaan-jaff]

Looks like a medium / large cc @yuneng-jiang

@mubashirosmani can you try to repro this ?