Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

HIP: "parallel": 2 + --layer-split on 2x R9700 exits (code 1) after "captured the batch window over slots 0,1"

Open
  • Is something wrong?
#890 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
machine-learning

Research direction

No source files or tests are named. Start by reproducing with the reported HIP setup, "parallel": 2, and layer_split "24", then use the offered debug build or full log to investigate the failure after captured the batch window over slots 0,1. Done means parallel decode with a HIP layer split completes without exiting with code 1.

Written by the indexing model from the issue text.

Description

Setup

  • Strata v0.1.39 (6f32ec0) built from source, HIP backend, gfx1201, TheRock ROCm 7.10 wheels, Ubuntu 26.04, kernel 7.0
  • 2x Radeon AI PRO R9700 (32 GB), Qwen3.8-Flash-Next IQ3_S
  • layer_split "24", --trim-stage-weights --mmap-experts, MTP --spec 4 — 100% of experts resident in VRAM

What happens
With "parallel": 2, the first time two requests decode together the engine exits with code 1 and no error message. Last log line:

strata verify: captured the batch window over slots 0,1

--batch-groups 2 crashes the same way (last line captured the batch window over slots 0).

What works

  • Same box single-lane: ~1,227 tok/s prompt (29K tokens), 52-64 tok/s decode, stable.
  • "parallel": 2 on a single R9700 (no split) — fine.
  • "parallel": 2 with a layer split on 3x RTX 5070 Ti (CUDA) — fine.

So it looks specific to batch decode + layer split on HIP. Happy to run a debug build or send the full log.

Dominant language
C++
Stars
11.6k
Forks
1k
Avg merge
7h 46m
Merged PRs (30d)
30

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from Niko1221/Strata

All issues in Niko1221/Strata

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.