rendered_ids shared across panesrendered_ids shared across panesFile: src/server/render.zig:664, src/server/render.zig:663–733
Severity: HIGH
Status: ✅ FIXED — rendered_ids is now allocated inside the for (bounds) loop, so deduplication is per-pane (each pane owns its own 64-slot ring buffer). A unit test (renderSixelImages renders sixel from every pane — bug #194) verifies two panes each storing an image in slot 0 both emit their DCS bytes.
var rendered_ids = [_]bool{false} ** 64; // declared ONCE, outside the bounds loop
for (bounds) |pb| {
...
if (!rendered_ids[slot]) { // keyed only by slot index
rendered_ids[slot] = true;
... self.writeBytes(img.data); ...
}
}
rendered_ids is allocated once per renderSixelImages call and keyed by slot (the registry index id % 64). Two different panes whose screens each hold a sixel image in slot 0 will collide: the first pane’s image is drawn and sets rendered_ids[0] = true; the second pane’s slot-0 image is then skipped entirely. Sixel silently disappears from every non-first pane that happens to use the same slot index. The flag must be per-pane (or keyed by &screen + slot).