Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
No issues found across 4 files
Shadow auto-approve: would not auto-approve. This PR does not meet the repository auto-approval settings.
Re-trigger cubic
There was a problem hiding this comment.
0 issues found across 2 files (changes from recent commits).
Shadow auto-approve: would not auto-approve. This PR does not meet the repository auto-approval settings.
Re-trigger cubic
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
No issues found across 4 files
Shadow auto-approve: would not auto-approve. This PR does not meet the repository auto-approval settings.
Re-trigger cubic
Large multi-frame images currently retain every decoded RGB frame before layout inference starts. Process each frame through inference immediately and close its converted buffer after the page completes. Page order, dimensions, format metadata and pixel contents are preserved.
Validation:
nick-oom-perf-oct01SND, same core-product API image digest, separate Linux pods limited to two CPU cores: three matched trials on 160 compressed 1024×1024 TIFF frames produce identical output hashes. Median decoding time is 0.392 → 0.176 seconds; peak process RSS is 869 → 232 MiB. This isolates decoding using an empty fixed layout; it is not an end-to-end model latency claim.OOMKilled(exit 137), while the candidate completes the same fixture.A corrupt later frame is now discovered after inference on earlier valid frames; the tested corrupt input raises the same exception and neither implementation returns a partial document. Decoded page layouts still accumulate in the returned document, so memory remains proportional to output size.
Release metadata targets 1.6.15. Sibling PRs take #518 → 1.6.14, #521 → 1.6.16 and #522 → 1.6.17; merging out of that order requires renumbering. Consumers require the resulting inference-library release to receive the fix.