mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Memory leak #2401
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#2401
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Aragur on GitHub (Jul 20, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
Description
Memory leaks extremely during normal operation.

Netdata Output:
👟 Reproduction steps
I don't know it. Just set it up, add some monitors (using Docker-Monitoring)
👀 Expected behavior
Don't Memory Leak
😓 Actual Behavior
Memory Leak
🐻 Uptime-Kuma Version
1.22.1
💻 Operating System and Arch
Linux 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.37-1 (2023-07-03) x86_64 GNU/Linux
🌐 Browser
Arc 0.112.0 (40064)
🐋 Docker Version
Docker 24.0.4
🟩 NodeJS Version
No response
📝 Relevant log output
📝 Configuration File
Click to expand
@louislam commented on GitHub (Jul 20, 2023):
Similar issue: #2344
Was unable to find the root cause. I will try to reproduce using your config.
@CommanderStorm commented on GitHub (Jul 20, 2023):
Your configuration has the domains redacted making reproducing this less eazy.
Could you share the URLs of the domains for which I wouldn't need Auth?
Given that it is mentioned in the log:
what is the URL of monitor 3?
@Aragur commented on GitHub (Jul 22, 2023):
@CommanderStorm sorry that's not that easy to expose these as this is used for internal monitoring only.
Monitor 3 is the URL of the currently running Uptime Kuma instance. So it's testing itself if it's up.
@CommanderStorm commented on GitHub (Jul 22, 2023):
I tested if this reproducable with a monitoring the website itsself.
(i.e. monitoring
http://localhost:3001/) => could not reproduce this issue.Currently, I am being unable to replicate this issue.
Given that the rest requires significant effort to reproduce, could you try these steps to make this into a Minimal, Reproducible Example:
pauseevery monitor and enable them one by one and noting which of them causes the significant memory leak?@CommanderStorm commented on GitHub (Dec 14, 2023):
Closing as unreproducible and @Aragur did not respond to further questions