You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bench: Move primitive-Signal benches to top of bench-signal.js
The fresh-take agents (Challenge + Survey + Neutral) all flagged that
set-same-10m and sub-unsub-100k regressing under reference safety is
inexplicable from the primitive-Signal hot path itself (protect()
early-returns before reading this.safety; bytecode is identical to
clone mode).
The convergent hypothesis is that the regression is inherited
cross-bench state: the upstream list-Signal benches do dramatically
different allocation/cloning work in clone vs reference mode, leaving
V8 with different JIT feedback / heap layout / GC pressure when the
primitive benches execute later in the same Chrome session.
Running the primitives first isolates them. If the regressions persist
at the top of the script, the cause is intrinsic to the primitive path.
If they disappear, the cause is cross-bench state — diagnostic, not a
production code change.
0 commit comments