Possible memory leaks

[Lanhild]

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

Often more than not, I have to restart my Uptime Kuma because of an exponentially increasing memory usage. Searched through the logs but I haven't found anything relevant. I have about ~60 HTTP monitors.

👟 Reproduction steps

Have an uptime kuma container on Docker.

👀 Expected behavior

No memory leaks

😓 Actual Behavior

Huge memory leaks over time.

🐻 Uptime-Kuma Version

1.20.1

💻 Operating System and Arch

Ubuntu 22.04

🌐 Browser

Irrelevant

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[louislam]

Similar issue: #2344

It is hard to fix as I cannot reproduce the issue. It will be great if you could provide more info on how to reproduce.

[Lanhild]

Seems like using a MongoDB monitor causes a very high memory usage/fluctuations. I had enabled a MongoDB monitor, and that's when the memory usage spikes started. I disabled it and now my memory usage seems to have come back to normal.

[milindpatel63]

I am also having a similar issue...
I am running uptime kuma on fly.io free plan...with 1GB disk space and 232MB of memory...it has been running fine for a year, but after the latest update, I had 2 crashes in the past week due to out of memory

[louislam]

I am also having a similar issue... I am running uptime kuma on fly.io free plan...with 1GB disk space and 232MB of memory...it has been running fine for a year, but after the latest update, I had 2 crashes in the past week due to out of memory

Using mongodb too?

[PeterCxy]

I have the same issue running uptime kuma on fly.io after updating to 1.20.1, and I am not using the MongoDB monitor. I am only using monitors of type HTTP, PING, DNS, or PUSH.

[chakflying]

Interesting that there is mention of a memory leak in MongoDB's JIRA which was fixed in the latest version.

[louislam]

Interesting that there is mention of a memory leak in MongoDB's JIRA which was fixed in the latest version.

Thanks, it should have a quick release for this.

[PeterCxy]

But the issue is also present for me without using the MongoDB monitor type. Is it triggered regardless of whether the MongoDB driver is actually used?

[louislam]

But the issue is also present for me without using the MongoDB monitor type. Is it triggered regardless of whether the MongoDB driver is actually used?

Probably not, would be appreciated if you could find the root cause of your issue.