OpenPipe / OpenPipe/ART

RuntimeError: torch.cuda.MemPool doesn't currently support expandable_segments during vLLM model initialization

Open
#405 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
10.8k
Forks
989
Avg merge
6h 29m
Merged PRs (30d)
85

Description

Description

Summary

When training a LangGraph agent with openpipe-art[backend,langgraph], the process fails at model initialization with the following error:

RuntimeError: torch.cuda.MemPool doesn't currently support expandable_segments.

The error occurs inside vLLM when allocating CUDA parameters during model initialization.

Environment

  • OS: Linux
  • GPUs: 2x NVIDIA L4 (23 GB each)
  • CUDA: 12.4 (nvcc --version shows Cuda compilation tools, release 12.4, V12.4.131)
  • NVIDIA driver: 550.90.07
  • Python: 3.12.x (venv with uv)
  • Installed via: pip install openpipe-art[backend,langgraph]
  • Dependency versions (from uv.lock):
    • torch==2.7.1
    • vllm==0.10.0

Steps to reproduce

  1. Create a new Python 3.12 virtual environment.
  2. uv add openpipe-art[backend,langgraph]>=0.4.11
  3. Run training (which calls art.model.register()).
  4. Observe the crash at model initialization.

Logs

File ".../vllm/model_executor/layers/vocab_parallel_embedding.py", line 34, in init
weight = Parameter(torch.empty(sum(output_partition_sizes), ...))
RuntimeError: torch.cuda.MemPool doesn't currently support expandable_segments.

Request

  • Please confirm if the current pinned torch (2.7.1) + vllm (0.10.0) combination is expected to work with CUDA 12.4 / L4 GPUs.
  • If not, could you provide a tested torch/vllm/xformers pinset for CUDA 12.4?
  • Alternatively, handle this error in vLLM (or document required versions) so users don’t hit this blocker.

Happy to provide full logs (pip freeze, nvcc, etc.) if needed.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with the reported Python 3.12, torch 2.7.1, vLLM 0.10.0, CUDA 12.4, and L4 environment, then inspect art.model.register() and the dependency pins in uv.lock. Compare compatible torch, vLLM, and xformers versions. Done means confirming a tested pinset or documenting the required versions and handling for this initialization error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
machine-learning
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.