FA-52933 / Raster memory layout / Member archive

Capture Ring Frame Slots: Capture fence overwrites final pixels or next slot header · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at fence_address.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

A capture ring holds four frame slots, each with an eight-byte generation header and image payload followed by a three-byte fence word. Frame generation maps monotonically to slot modulo capacity; byte addresses use slot, freshness uses full generation. Return the named intermediate layout descriptor and final address fields; all quantities are integer byte offsets unless explicitly stated.

Why this case matters

Offline raster resource, upload, readback, and storage-layout regression model.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
layout fixture 1	`{"allocation_end": 93, "fence_address": 37, "fresh": false, "payload_bytes": 4, "read_address": 86, "read_header": 78, "read_slot": 3, "slot_pitch": 15, "write_header": 33, "write_slot": 0}`	`{"allocation_end": 93, "fence_address": 45, "fresh": false, "payload_bytes": 4, "read_address": 86, "read_header": 78, "read_slot": 3, "slot_pitch": 15, "write_header": 33, "write_slot": 0}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.