FAILURE MAP
← Case archive

FA-52882 / Raster memory layout / Member archive

Packed 422 Macropixels: Macropixel validity includes padding luma or drops every second pixel · case 02

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

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

A stipulated 4:2:2 image stores each pair as [Y0,U,Y1,V], with two bytes per component. Odd final pairs still reserve both luma slots. Three-byte row prefixes precede complete macropixels. 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 fixtureActualExpectedOutcome
layout fixture 1{"address": 25, "allocation_end": 33, "component_lane": 0, "luma_lane": 0, "pair_id": 0, "pair_origin": 25, "pairs": 1, "row_origin": 25, "row_pitch": 11, "valid_luma_slots": 2}{"address": 25, "allocation_end": 33, "component_lane": 0, "luma_lane": 0, "pair_id": 0, "pair_origin": 25, "pairs": 1, "row_origin": 25, "row_pitch": 11, "valid_luma_slots": 1}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.

Sign in to the archive ↗