The review's items: a zero-content open continuation bills 0 but still pushed '' into the held fragment array, so a forged empty-open flood grew host memory without touching the ledger — the push is now skipped (an empty fragment contributes nothing to the merged entry). The spawn-site comment said a PATH change between load and run would fail with ENOENT; it actually makes spawn throw synchronously, which the surrounding try settles as worker-exit. |
||
|---|---|---|
| .. | ||
| index.ts | ||
| invariant.ts | ||
| protocol.ts | ||