Issues

perf: json_pipeline at 500k records is 97.6x bun (60.4s vs 618ms) while the same workload at 100 records BEATS bun — a scaling cliff, not a constant factor

#7592

· proggeramlug opened

on Aug 7, 2026

test-parity: known_failures.json is a pure suppression list — a stale entry hid a data-loss bug for six days

#7582

· proggeramlug opened

on Aug 7, 2026

perf: re-profile of construction on v0.5.1325 — typed_shape_layout_entry ~25% is the new top lever, js_array_length ~10-15% is unexplained

#7578

· proggeramlug opened

on Aug 7, 2026

`instanceof` a Map/Set SUBCLASS is false (`m instanceof MyMap`); only the native base edge survives

#7575

· proggeramlug opened

on Aug 7, 2026

class X extends Array in an `T[]`-annotated binding takes the raw ArrayHeader fast paths (sibling of #7570)

#7574

· proggeramlug opened

on Aug 7, 2026

gc: 05_closure_capture retains +16.44% with every collector counter at +0.00% — surfaced when the ratchet started measuring again

#7559

· proggeramlug opened

on Aug 7, 2026

gc(): the forced conservative stack scan makes every retained-heap reading nondeterministic, and 16% too large on a 50 MB live set

#7558

· proggeramlug opened

on Aug 7, 2026

security-audit is a REQUIRED context, red on main, so every merge bypasses it — 2 real advisories (lopdf 7.5 HIGH, rkyv), and #7412 does not fix them

#7555

· proggeramlug opened

on Aug 7, 2026

gc-ratchet has measured nothing since 2026-08-05: harness validation fails before the probes run (12_large_live_set spread 6768)

#7554

· proggeramlug opened

on Aug 7, 2026

spread: a replaced `Array.prototype[Symbol.iterator]` is ignored by `[...arr]`

#7542

· proggeramlug opened

on Aug 6, 2026

spread: `[...arr]` on a `class X extends Array` instance throws "value is not iterable"

#7541

· proggeramlug opened

on Aug 6, 2026

addr-class: eight sites still classify heap addresses by magnitude floor, not by band (the #7526 idiom)

#7531

· proggeramlug opened

on Aug 6, 2026

Navigation Menu

Uh oh!

Uh oh!

All issues

perf: json_pipeline at 500k records is 97.6x bun (60.4s vs 618ms) while the same workload at 100 records BEATS bun — a scaling cliff, not a constant factor

test-parity: known_failures.json is a pure suppression list — a stale entry hid a data-loss bug for six days

perf: re-profile of construction on v0.5.1325 — typed_shape_layout_entry ~25% is the new top lever, js_array_length ~10-15% is unexplained

`instanceof` a Map/Set SUBCLASS is false (`m instanceof MyMap`); only the native base edge survives

class X extends Array in an `T[]`-annotated binding takes the raw ArrayHeader fast paths (sibling of #7570)

gc: 05_closure_capture retains +16.44% with every collector counter at +0.00% — surfaced when the ratchet started measuring again

gc(): the forced conservative stack scan makes every retained-heap reading nondeterministic, and 16% too large on a 50 MB live set

security-audit is a REQUIRED context, red on main, so every merge bypasses it — 2 real advisories (lopdf 7.5 HIGH, rkyv), and #7412 does not fix them

gc-ratchet has measured nothing since 2026-08-05: harness validation fails before the probes run (12_large_live_set spread 6768)

spread: a replaced `Array.prototype[Symbol.iterator]` is ignored by `[...arr]`

spread: `[...arr]` on a `class X extends Array` instance throws "value is not iterable"

addr-class: eight sites still classify heap addresses by magnitude floor, not by band (the #7526 idiom)

Uh oh!

Uh oh!

Search results