Heads up, we were seeing a memory leak issue on v0.20. We’ve upgrade to v.0.25, so hoping something in there might solve the problem. It’s pretty minimal so we figure kicking the box every ~2 weeks is a good solution for now.

Thanks for reporting. How are you deploying Cerbos?

We build an image in ECR and deploy it via ECS. We’re managing it all via CDK.

Thanks - there have a been a number of changes between 0.20 and 0.25 so let us know if you start seeing the same trend and we can try and dig into it

Will do, was reading the change-log and looks like there’s been a bunch 🤞

Specifically there were some updates to how the cache evicted over time which could be related to this

I’ll set a reminder to check back in a few days

Hi. Has it ever reached 100% and crashed? Some times things look like a memory leak but that's simply because the memory is not immediately released back to the OS because there's no memory pressure.

Not 100% and crashed, but we noticed it today because we started seeing errors from the cerbos service

Yeah. It's been running continuously for almost a month before that, hasn't it?

We got GRPC errors in our primary application when calling the Cerbos service

What's the memory limit you have set on the container? If you have a staging/dev environment, I'd suggest setting a lower limit and seeing if the usage keeps rising over 100%. So far I haven't been able to reproduce the issue.