To Reproduce
- Open the logs view.
- Continuously load or generate logs without limit.
- Observe browser memory and UI responsiveness degrading over time.
Current vs. Expected behavior
The logs view should automatically restrict the number of visible log items to prevent DOM overload, keeping the browser responsive regardless of the total log volume.
Provide environment information
OS: Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-133-generic x86_64)
Arch: x64
Dokploy version: 0.21.8
VPS Provider: OVH Baremetal
Application: NodeJS
Which area(s) are affected? (Select all that apply)
Application
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
Description:
Currently, the logs view renders an unbounded number of log entries in the DOM. When the number of log elements grows too large (in my case, exceeding 7,000+ DOM nodes), the browser becomes extremely slow or completely unresponsive due to DOM overload and rendering issues.
This causes performance degradation and eventually freezes the browser tab, making it unusable for reviewing logs in large volumes.
Proposed solution:
Implement a hard or configurable limit on the maximum number of logs rendered at once (e.g., 100, 500, 1,000 lines). Older logs can be truncated or removed as new logs arrive, keeping the total number of rendered elements within a reasonable range.
Will you send a PR to fix it?
Maybe, need help
To Reproduce
Current vs. Expected behavior
The logs view should automatically restrict the number of visible log items to prevent DOM overload, keeping the browser responsive regardless of the total log volume.
Provide environment information
Which area(s) are affected? (Select all that apply)
Application
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
Description:
Currently, the logs view renders an unbounded number of log entries in the DOM. When the number of log elements grows too large (in my case, exceeding 7,000+ DOM nodes), the browser becomes extremely slow or completely unresponsive due to DOM overload and rendering issues.
This causes performance degradation and eventually freezes the browser tab, making it unusable for reviewing logs in large volumes.
Proposed solution:
Implement a hard or configurable limit on the maximum number of logs rendered at once (e.g., 100, 500, 1,000 lines). Older logs can be truncated or removed as new logs arrive, keeping the total number of rendered elements within a reasonable range.
Will you send a PR to fix it?
Maybe, need help