Potential memory leak when showing volume backup (deployment) logs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
To Reproduce
- Add a volume backup to an application that produces a large log file (e.g. backing up a large application with 40k+ files, resulting in a log of 40k+ entries)
- Run volume backup
- Click the show deployments button on the volume backup
- Click view on the latest run to see the log
Current vs. Expected behavior
When viewing log entries in the dialog as described above, large log files (40k+ lines) result in a significant slow down of the UI and the browser, as it is trying to create HTML nodes for each. And this can only be escaped by force-quitting the browser tab or exiting the browser itself.
Since log files can be very large, the view should use a virtualized list instead.
Provide environment information
Dokploy <= v0.29.8 on a VPS
Accessed through Firefox 151.0.4
Looking at volume backup logs of a NextCloud instance
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
No response
Will you send a PR to fix it?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the volume backup deployment-log dialog reached through Show deployments and View on the latest run. Reproduce it with a 40k+ entry log, then replace the full HTML-node rendering with a virtualized list; done means the log remains usable without severe browser slowdown or requiring the tab to be force-quit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100