Large Monorepo OOM Errors with Turbosnap Enabled

[ChrisSargent]

Bug report

We are seeing OOM errors during the Chromatic build process if we have Turbosnap enabled. In particular this seems to happen if there's any package.json change causing a change to the yarn.lock file.

We have tried setting max-old-space pretty high but it still happens.

Critical Logs are below, nothing interesting in the stacktrace.

Found 99 manifest/lockfile pairs to diff

<--- Last few GCs --->

[4282:0x6cc28b0]   194031 ms: Scavenge (reduce) 3924.3 (4142.0) -> 3923.9 (4142.3) MB, 5.7 / 0.0 ms  (average mu = 0.144, current mu = 0.066) allocation failure; 
[4282:0x6cc28b0]   194042 ms: Scavenge (reduce) 3924.8 (4142.3) -> 3924.4 (4142.5) MB, 5.2 / 0.0 ms  (average mu = 0.144, current mu = 0.066) allocation failure; 
[4282:0x6cc28b0]   194051 ms: Scavenge (reduce) 3925.2 (4142.5) -> 3924.8 (4142.8) MB, 4.8 / 0.0 ms  (average mu = 0.144, current mu = 0.066) allocation failure; 


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
Aborted (core dumped)

This started happening after this upgrade (and we also started getting errors about the traceChanged option seemingly changed from expand to expanded.

[cgbl-90]

hello @ChrisSargent have you tried the workarounds described here: Why is my build failing with an Out of memory error?

[ChrisSargent]

Hi @cgbl-90 - yes, we have 4gb of max old space size set in NODE_OPTIONS. We run in to the same issues locally on 16GB ram macbook pros.

FYI, we've also trying setting the max old space size much higher but it eventually dies.