66414dedd3
A search_files hit inside a serialized dump (multi-MB single-line JSON, minified bundle) made rg/grep emit the entire matched line into stdout: head -n counts lines, so a 40MB match line crossed the exec transport untruncated and was buffered whole into Python before the per-match [:500] clamp ran. Measured on main: 42MB transport payload and ~180MB peak Python allocation for a single match. Fix at the engine layer, all three pipelines: - rg: --max-columns 2000 --max-columns-preview (preview keeps the match visible instead of omitting it) - grep fallback + darwin pruned-grep fallback: | cut -c1-2000 - files_only/count modes skipped (lines are paths/counts, never giant) 2000 cols exceeds the existing 500-char content clamp, so no previously-visible content changes. Adapted from cline/cline#13525 (search_codebase RangeError OOM crash on giant single-line files) — hermes buffers in Python rather than a JS string, so the failure mode is memory/transport blowup rather than an uncaughtException, but the class is identical.