mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Tab crashes due to out-of-memory #4602
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#4602
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 @AlyoshaVasilieva on GitHub (Jan 13, 2026).
📑 I have found these related issues/pull requests
I saw https://github.com/louislam/uptime-kuma/issues/6420 but that specifies Firefox. This happens in Chrome.
🛡️ Security Policy
📝 Description
Leaving the Uptime Kuma dashboard open for a long time (I keep my browser open for ~days at a time) ends up crashing due to OOM.
👟 Reproduction steps
edit: Since opening this issue (and restarting the tab) 4 hours ago, tab memory usage has climbed from ~180MB to ~550MB.
edit: At the 7 hour mark, it's at ~870MB.
👀 Expected behavior
It shouldn't use more and more memory.
😓 Actual Behavior
It uses more and more memory until crashing.
🐻 Uptime-Kuma Version
2.0.2
💻 Operating System and Arch
Uptime-Kuma host is Debian 13, browser running on Windows 10
🌐 Browser
Chrome 143.0.7499.170 x64
🖥️ Deployment Environment
29.1.3(Buildf52814d)32📝 Relevant log output