v3.24.0 constantly runs out of memory

[timconsidine]

Never had a problem with Umami before.
I had it set at 2Gb RAM which is a healthy amount for this kind of app (even maybe high).
Auto-upgrade to Cloudron v3.24.0 immediately brought repeat OOM
Increased it - reluctantly - to 3Gb.
Still crashing.

Checked redid for umami - running at 15% (40/256) - restarted it anyway.

Now umami is not responding.

Anyone else seeing this ?
Don't see any relevant GitHub issues for upstream 3.1.0

[shrey]

Yeah, same here. Had to roll back to the last version.

[ccfu]

Had this as well several times after uodate, but it seems to have stabilised. No OOM for the past 8 hours.

[timconsidine]

Cloudron Team : I am not clear whether cloudron 3.24.0 used a different upstream base 3.1.0 to previous, but my impression is not. So the issue is in cloudron v3.24.0 ? Can it be fixed ?

[james]

Hello @timconsidine
These are the changes made https://git.cloudron.io/packages/umami-app/-/commit/4e3d31c2f37285960d017fd157956b5aae9138ef

One thing that jumps at me is --max-old-space-size=4096.

The container runs a full Next.js production yarn build on every start (see start.sh:L35).
Next.js builds are notoriously memory-hungry; they scale with the size of the app bundle.
Node is told --max-old-space-size=4096 (4 GiB V8 heap) while the cgroup hard cap from CloudronManifest.json:L13 is 2 GiB by default.
Node happily tries to grow past 2 GiB, the kernel OOM-kills the container.

This value should not be hard coded, instead should reflect the memory limit set by the user.
An app update will be available soon.