Policy Collapse and Gibberish Rollouts in Search-R1 Early Training when TIS is Enabled (3B Model)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.5k
- Forks
- 1.3k
- Avg merge
- 5h 36m
- Merged PRs (30d)
- 22
Description
When reproducing Search-R1 using a 3B model on the Slime framework, I encountered a policy collapse during the early stages of training specifically when Token Importance Sampling (TIS) is enabled. I followed the tutorial settings in Enabling TIS (Trajectory Importance Sampling)
The model starts to generate chaotic, multilingual gibberish and completely ignores the system prompt and formatting constraints (e.g., and tags).
Comparison: TIS ON vs. OFF
TIS Enabled: The model collapses within the first few rollouts. Outputs become high-entropy "word salad" (as shown in the logs below).
TIS Disabled: Training is stable. The model follows the prompt instructions and converges normally.
In the early rollouts, the model fails to maintain the reasoning format and generate abnormal outputs:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Search-R1 tutorial's “Enabling TIS (Trajectory Importance Sampling)” settings and reproduce the 3B-model run in Slime with TIS enabled and disabled. Compare the early rollout logs and generated outputs, focusing on policy collapse, prompt adherence, and the / formatting. Done means the TIS-enabled run no longer produces gibberish or collapses during early rollouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100