I have a few huge log files. I would like to check for the presence of 'RuntimeError:…
- User
I have a few huge log files. I would like to check for the presence of 'RuntimeError: CUDA out of memory' in each log file. How do I do this?
- Assistant
Here are several quick, memory-friendly ways to scan one—or many—large log files for the exact text
RuntimeError: CUDA out of memory
──────────────────────────────────────────────────────────────────────────────
- One-liner with plain GNU grep ──────────────────────────────────────────────────────────────────────────────
Show every matching line, prefixed by the file name and line number
grep -HnF 'RuntimeError: CUDA out of memory' /path/to/logs/*.log
Options used
• -H – always print the file name
• -n – print the line number(s)
• -F – fixed-string search (faster; no regex parsing)────────────────────────────────────────────────────────────────────────────── 2. Only list the files that contain the error ────────────────────────────────────────────────────────────────────────────── grep -lF 'RuntimeError: CUDA out of memory' /path/to/logs/*.log
-l (lower-case L) stops reading the file after the first hit and just prints the file name.
Ideal when you only care about presence/absence.────────────────────────────────────────────────────────────────────────────── 3. Script-style loop (useful when logs are scattered in many dirs) ────────────────────────────────────────────────────────────────────────────── #!/usr/bin/env bash for f in /path/to/logs/**/*.log; do # ** requires shopt -s globstar in Bash ≤4 if grep -qF 'RuntimeError: CUDA out of memory' "f" fi done
Flags
• -q – quiet; exit status only (0 = found, 1 = not found)
The loop prints the file name only when the pattern exists.────────────────────────────────────────────────────────────────────────────── 4. Compressed logs? → zgrep ────────────────────────────────────────────────────────────────────────────── zgrep -HnF 'RuntimeError: CUDA out of memory' /path/to/logs/*.log.gz
────────────────────────────────────────────────────────────────────────────── 5. Even faster tools (optional) ────────────────────────────────────────────────────────────────────────────── ripgrep (rg) is orders of magnitude quicker on giant directories:
rg --fixed-strings --line-number 'RuntimeError: CUDA out of memory' /path/to/logs
────────────────────────────────────────────────────────────────────────────── Exit codes for automation ────────────────────────────────────────────────────────────────────────────── grep -qF 'RuntimeError: CUDA out of memory' big.log echo $? # 0 → pattern found, 1 → not found, ≥2 → error
Use this in CI pipelines or cron jobs to fail builds when OOM errors appear.
────────────────────────────────────────────────────────────────────────────── Summary ────────────────────────────────────────────────────────────────────────────── • Simple grep works fine even on multi-GB files because it streams data line-by-line.
• Use -F (fixed string) and -l / -q when you only need a yes/no answer.
• For .gz archives, swap grep → zgrep.
• For the fastest searches across thousands of files, try ripgrep (rg).That’s it—pick the variant that fits your workflow!
- User
What if the log file ends in .gz?
- Assistant
No need to unpack the logs first—just let the “z-family” tools stream-decompress on the fly.
Quickest one-liners
Show every matching line, with file-name + line number:
zgrep -HnF 'RuntimeError: CUDA out of memory' /path/to/logs/*.gzOnly list the
.gzfiles that contain the error (stops after first match in each file):zgrep -lF 'RuntimeError: CUDA out of memory' /path/to/logs/*.gz(The flags are identical to
grep; the leading z is the only difference.)Looping example
#!/usr/bin/env bash for f in /path/to/logs/**/*.gz; do # enable globstar if needed if zgrep -qF 'RuntimeError: CUDA out of memory' "$f"; then echo "❌ Found in: $f" fi donePortable alternatives
If your system lacks
zgrep:for f in /path/to/logs/*.gz; do gunzip -c "$f" | grep -qF 'RuntimeError: CUDA out of memory' && echo "$f" done(macOS has
gzcatinstead ofzcat.)Even faster searchers
• ripgrep 13+ auto-decompresses
.gz:rg --fixed-strings 'RuntimeError: CUDA out of memory' /path/to/logs/*.gz•
zstdgrep/xzgrepexist for other compressed formats.Key point
All of these commands stream; they never expand the entire file to disk or RAM, so they work fine on multi-gigabyte compressed logs.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.