# general


12/19/2023, 1:19 AM
Hey all, not sure if this is an esbuild question or a pulumi question... but running into an issue where doing a pulumi up/preview on a repo with about 10 or so lambdas is creating a 15GB memory esbuild process. Has anyone happened to have run into this before or have some pointers to solutions?
As usual immediately after asking for help I figure out a solution, using buildSync instead of await build in esbuild fixed everything