Skip to content

[BUGFIX] fix value oom in radix tree#17400

Merged
ispobock merged 1 commit intomainfrom
yizhang/fix_radix_cache_oom
Jan 21, 2026
Merged

[BUGFIX] fix value oom in radix tree#17400
ispobock merged 1 commit intomainfrom
yizhang/fix_radix_cache_oom

Conversation

@yizhang2077
Copy link
Copy Markdown
Collaborator

Motivation

fix missing part in #17191

Modifications

Accuracy Tests

Benchmarking and Profiling

Checklist

Review Process

  1. Ping Merge Oncalls to start the PR flow. See the PR Merge Process.
  2. Get approvals from CODEOWNERS and other reviewers.
  3. Trigger CI tests with comments or contact authorized users to do so.
    • /tag-run-ci-label, /rerun-failed-ci, /tag-and-rerun-ci
  4. After green CI and required approvals, ask Merge Oncalls to merge.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @yizhang2077, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a potential Out-Of-Memory (OOM) issue within the radix tree cache by modifying how values are assigned to tree nodes. The core change involves introducing explicit cloning for host_value and value objects when they are stored in new or updated tree nodes. This ensures that each node holds an independent copy of its associated data, preventing unintended shared references that could lead to memory leaks or incorrect state, thereby completing a previous fix.

Highlights

  • Memory Management: Introduced cloning for host_value when creating new nodes in _insert_helper_host to prevent shared references and potential Out-Of-Memory (OOM) issues.
  • Radix Tree Value Handling: Ensured value is cloned when assigned to new TreeNode instances or updated in shared-prefix nodes within the insert method, guaranteeing independent copies.
  • Mamba Radix Cache Consistency: Applied similar cloning logic for value in mamba_radix_cache.py during node insertion to maintain consistent memory management across different radix tree implementations.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@xiezhq-hermann xiezhq-hermann self-assigned this Jan 20, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request introduces .clone() calls when assigning value and host_value to TreeNode properties. This is a crucial change that addresses potential data corruption and out-of-memory (OOM) issues by ensuring that new nodes receive independent copies of tensor data rather than shared references. This prevents unintended modifications to node data when the original tensors or their slices are altered elsewhere in the program. The consistent application of .clone() across different insertion points in both hiradix_cache.py and mamba_radix_cache.py indicates a thorough fix for aliasing problems with mutable tensor values.

@ispobock
Copy link
Copy Markdown
Collaborator

/tag-and-rerun-ci

@ispobock ispobock merged commit 1b97fa7 into main Jan 21, 2026
196 of 221 checks passed
@ispobock ispobock deleted the yizhang/fix_radix_cache_oom branch January 21, 2026 09:13
gmixiaojin pushed a commit to gmixiaojin/sglang that referenced this pull request Jan 21, 2026
@ispobock ispobock mentioned this pull request Mar 8, 2026
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants