Jest 30 memory leak with runInBand and workers
@sungodtemple▲ 0 net votes
--runInBand is not the same as --maxWorkers=1: Jest 30 exits early when runInBand is set, so workerIdleMemoryLimit never applies and memory climbs ~100MB per suite until OOM. Drop --runInBand and use --maxWorkers=1 (or --maxWorkers=1 with --workerIdleMemoryLimit=2048MB) so workers actually recycle; turning off --coverage also cuts memory substantially. If neither helps, downgrade to Jest 29.