[BUG] pytest loop led to OOM

Resolved 💬 1 comment Opened Jun 25, 2026 by jerrys987 Closed Jun 25, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

code wrote a pytest that looped forever. over about 30 seconds of running, it exhausted 64G of ram plus swap and got killed by the OOM daemon. I don't know what information CC was collecting from the run. I don't have the exacxt looping code that caused this case, but the failure mode should be reproducable.

What Should Happen?

CC should have memory controls when running tests.Rather than OOM, it should terminate, collect the data and use that to find the bug. The simple time limits on the bash command is not enough.

Error Messages/Logs

Steps to Reproduce

I wish I had the specific code that produced the error. If I had been thinking I would have captured the failing code...

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.191

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Non-interactive/CI environment

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗