FA-90807 / Garbage collector invariants / Member archive

Oop maps: run count used as an end index · case 02

Reference runs that start beyond their count scan nothing, so referenced objects are missed.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Precise tracing with per-class reference maps. Objects are word lists: words 0-1 are the header; object arrays keep their length in word 2 and elements in words 3..3+len-1 (anything after is padding); primitive arrays contain no references. Instance classes list [offset, count] runs of reference words and inherit all superclass runs. A reference word of 0 is null; a nonzero reference that is not an object id is reported as [object, word]. Return the reachable ids and the bad references.

Why this case matters

Tracing must follow exactly the reference words described by type metadata, no more and no less.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
regression: trace through fields, arrays and subclasses	`{"bad": [], "live": [100]}`	`{"bad": [], "live": [100, 101, 102, 103, 104, 107]}`	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.