From 00c56a4ca3fd938ebec2933ca3308aadbe4da6af Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Thu, 29 Oct 2026 14:27:42 -0300 Subject: Store.zig: an output pane too big to keep is skipped before its dump, not after Closing a 256 MiB +Pager base64'd and serialized its text (8.5 s in Debug, the session answering nothing meanwhile) only to throw the record away: an output pane's record always holds its text whole, so its length decides first. fs.py's remove of that pane timed out on it. Co-Authored-By: Claude Opus 5.5 --- src/Store.zig | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'src') diff --git a/src/Store.zig b/src/Store.zig index 5e47d695..856a7fc1 100644 --- a/src/Store.zig +++ b/src/Store.zig @@ -498,6 +498,10 @@ pub fn keep(s: *Store, p: *Pardes, id: usize) ?Kept { const pane = p.panes[id] orelse return null; if (pane.fs.unannounced or pane.query != null) return null; if (pane.file) |f| if (f.output) |o| if (o.from == .preview) return null; + // An output pane's record holds its text whole (base64): one past the + // bound is known before a dump of it is made, which for a 256 MiB + // +Pager held the session up for seconds only to be thrown away. + if (pane.file) |f| if (f.output != null and f.content.len > max_record) return null; const gpa = p.recentGpa(); const arena = p.scratch.allocator(); var dp = dump.dumpPane(p, arena, pane) catch return null; -- cgit v1.3