Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] ultrareview: crashed before producing findings on large PR" [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54831•Fetched 2026-04-30 06:34:43
View on GitHub
Comments
1
Participants
2
Timeline
10
Reactions
0
Author
alexboiialexboii
Participants
alexboiialexboiigithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×6cross-referenced ×2commented ×1unlabeled ×1

Error Message

{"error":"Review crashed before producing findings. See session logs for details."} Either findings, or a clear error explaining what went wrong (timeout, size cap, parser failure, etc.) so the user knows whether to retry or restructure the PR.

  1. Surface a real error (size limit hit / OOM / parse error / etc.) instead of the generic crash message /ultrareview should either return findings or surface a real, actionable error (e.g. "PR exceeds size cap of N files / N lines"). The user should know whether to retry, restructure the PR, or wait — and ideally not be billed for crashes that produce no output.

Error Messages/Logs

{"error":"Review crashed before producing findings. See session logs for details."} 4. Observe the only output is the generic crash error above. No findings, no partial output, no traceback.

Root Cause

Likely a size-related crash — smaller PRs in the same repo work normally; this one is unusually wide because it's a folded stack. Could be a memory cap, file-count cap, diff-size cap, or per-file timeout in the review pipeline.

Code Example

{"error":"Review crashed before producing findings. See session logs for details."}

---

{"error":"Review crashed before producing findings. See session logs for details."}
(That's all the client got — the user has no way to read the session logs themselves.)
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

Title

ultrareview: "Review crashed before producing findings" on large folded PR (no usable output)

What happened

Ran /ultrareview 13777 against housing-cloud/web#13777. The job completed (status went to completed, billing hit), but the only output was:

{"error":"Review crashed before producing findings. See session logs for details."}

Re-ran it; same result. No findings, no partial output, no stack trace surfaced to the client.

Repro

Expected

Either findings, or a clear error explaining what went wrong (timeout, size cap, parser failure, etc.) so the user knows whether to retry or restructure the PR.

Actual

Generic "Review crashed before producing findings. See session logs for details." with no actionable detail. The user has no way to read the session logs themselves.

Suspected cause

Likely a size-related crash — smaller PRs in the same repo work normally; this one is unusually wide because it's a folded stack. Could be a memory cap, file-count cap, diff-size cap, or per-file timeout in the review pipeline.

Asks

  1. Surface a real error (size limit hit / OOM / parse error / etc.) instead of the generic crash message
  2. If there's a size cap, document it and bail early with a "PR too large for ultrareview" message before billing
  3. Investigate the two linked sessions for the actual stack trace

Environment

  • Claude Code CLI on macOS (darwin 24.1.0)
  • Repo: housing-cloud/web (private), branch feat-reports-v2-reports-db, base main

What Should Happen?

/ultrareview should either return findings or surface a real, actionable error (e.g. "PR exceeds size cap of N files / N lines"). The user should know whether to retry, restructure the PR, or wait — and ideally not be billed for crashes that produce no output.

Error Messages/Logs

{"error":"Review crashed before producing findings. See session logs for details."}
(That's all the client got — the user has no way to read the session logs themselves.)

Steps to Reproduce

  1. In a Claude Code session, run /ultrareview <PR#> against an unusually large PR (e.g. a Graphite stack folded via gt fold --close into a single branch).
  2. PR shape in our case: 69 commits, 202 files changed, +51,640 / -397 lines.
  3. Wait ~5–10 min for the cloud job to complete.
  4. Observe the only output is the generic crash error above. No findings, no partial output, no traceback.

Reproduced twice in a row against the same PR (housing-cloud/web#13777). Sessions for log access:

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.123

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

No response

extent analysis

TL;DR

The issue can be addressed by investigating the session logs for the actual stack trace and error message to determine the root cause of the crash, which is likely related to the large size of the PR.

Guidance

  • Investigate the session logs for the actual stack trace and error message to determine the root cause of the crash.
  • Check if there are any size limits or caps in the review pipeline that could be causing the crash, such as a memory cap, file-count cap, diff-size cap, or per-file timeout.
  • Consider restructuring the PR to reduce its size, if possible, to see if that resolves the issue.
  • If the issue is due to a size cap, consider documenting the cap and implementing an early bail-out mechanism to prevent billing for crashes that produce no output.

Example

No code snippet is provided as the issue is related to the Claude Code CLI and its interaction with the Anthropics API, and no specific code changes are implied.

Notes

The issue is likely related to the large size of the PR, which is causing the review pipeline to crash. The session logs may provide more information about the root cause of the crash. The user has no way to read the session logs themselves, which makes it difficult to determine the root cause.

Recommendation

Apply workaround: Investigate the session logs and consider restructuring the PR to reduce its size, if possible, to see if that resolves the issue. This is because the issue is likely related to the large size of the PR, and reducing its size may prevent the crash.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#GPU compatibility#latency issue#model loading#dependency error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] ultrareview: crashed before producing findings on large PR" [1 comments, 2 participants]