Ricardo db10d9cfbf fix(og): batch spawning to prevent OOM during watcher rebuilds ...

Full OG regeneration (2,350 images) OOM-kills when the Eleventy watcher
is running (~1.8 GB RSS), leaving only ~1.2 GB headroom in the 3 GB
container. WASM native memory from Satori/Resvg grows beyond what GC
can reclaim within a single process.

Solution: spawn og-cli in batches of 100 images. Each invocation exits
after its batch, fully releasing all WASM native memory. Exit code 2
signals "more work remains" and the spawner re-loops. Peak memory per
batch stays under ~500 MB regardless of total image count.

Also seed newManifest from existing manifest so unscanned entries survive
batch writes.

Confab-Link: http://localhost:8080/sessions/edb1b7b0-da66-4486-bd9c-d1cfa7553b88

2026-03-09 17:37:17 +01:00

..

og-cli.js

fix(og): batch spawning to prevent OOM during watcher rebuilds

2026-03-09 17:37:17 +01:00

og.js

fix(og): batch spawning to prevent OOM during watcher rebuilds

2026-03-09 17:37:17 +01:00

unfurl-shortcode.js

perf: address PageSpeed Insights issues (CLS, contrast, touch targets, JS minification)

2026-03-07 20:13:45 +01:00