No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

We are seeing a lot of our deployments failing with a `[1]    28272 killed     pulumi up`

Downgrading the CLI version in out github action seemed to solve it

`3.48.0` also works fine, it’s a memory leak introduced in `3.49.0`

HI Yoav and Dotan, thanks for reporting the issue!

you can set "PULUMI_OPTIMIZED_CHECKPOINT_PATCH" to "0" to work with the latest version of the CLI.

And thanks <@UPSGP85A7> for creating the issue! <https://github.com/pulumi/pulumi/issues/11650>

Just note that I suspect this is the reason, but it would be really good to have someone confirm that setting that env var fixes things!

I just started a deployment with latest and `PULUMI_OPTIMIZED_CHECKPOINT_PATCH` , will update very soon!

it works fine with `PULUMI_OPTIMIZED_CHECKPOINT_PATCH`  :tada:

Out of interest could you run `pulumi stack export  | wc -c` and let me know how big the state for this deployment was?