Description
When building dotnet runtime on CI, we run OOM on WASM legs.
Top offenders are
GenerateDepsFileis at 25GB over 1056 runs on the same build. 😮ValidateAssembliesTask0.5GB over 59 runsResolveRuntimePackAssets0.4GB over 451 runs
The issue was identified by using new MSBuild telemetry
It would be good to fix the root cause (memory consumption) in those Tasks.
I believe that customers with large solutions could suffer with the same problems.
Workaround
We applied workaround to run those tasks out-of-process for WASM leg.