Skip to content

Dev/ida streaming memory#1

Merged
buzzer-re merged 3 commits into
mainfrom
dev/ida-streaming-memory
Jun 10, 2026
Merged

Dev/ida streaming memory#1
buzzer-re merged 3 commits into
mainfrom
dev/ida-streaming-memory

Conversation

@buzzer-re

Copy link
Copy Markdown
Owner

No description provided.

codex and others added 3 commits June 7, 2026 21:24
Resolve out-of-memory kills and silent phases when exporting large
already-analyzed databases (e.g. PS5 kernel .i64), without ever
re-running auto-analysis on an existing database.

- Place per-worker IDA database copies on durable on-disk storage
  (cache root, overridable via TOCODE_WORKER_TMP_DIR) instead of the
  system temp dir, which is frequently RAM-backed tmpfs; copying a
  multi-gigabyte database there pinned memory and OOM-killed the export.
- Skip the worker copy entirely when a single worker renders by opening
  the prepared database in place.
- Size the auto IDA worker budget from the database size so a huge
  database does not over-subscribe RAM.
- Log "Loading <binary>" before constructing the backend session so the
  database open/load is no longer a silent gap.
- Drop the per-cluster render log that flooded output and broke the
  progress bar.
- Report the metadata phase with a stepped progress bar and copy the
  published database in chunks with a byte progress bar.
- Annotate _resolve_thunk to clear the mypy annotation-unchecked note.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@buzzer-re buzzer-re merged commit 11af395 into main Jun 10, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants