CXwudi
commented
2 months ago Translation of this issue for English speakers:
qBittorrent Memory Leak When Using PeerBanHelper
Version
v6.0.1
OS and CPU Arch
Debian 12, X86
Deploy method
Official Docker Image
Downloader Type
qBittorrent
Issue Description
Several times, I've noticed qBittorrent's memory usage continuously increasing while downloading torrents, eventually leading to the entire Debian server crashing.
Inspired by the issue https://github.com/qbittorrent/qBittorrent/issues/18830, I discovered that after disabling PeerBanHelper, qBittorrent's memory usage stabilized.
Reproduce steps
Use the following docker-compose file to launch a reproducible instance:
services:
qbittorrent-app:
image: lscr.io/linuxserver/qbittorrent
container_name: qbittorrent-app
restart: unless-stopped
network_mode: host # to eliminate double-nat and make upnp working
environment:
#- PAGID=10000
- PGID=1000
- PUID=1000
- WEBUI_PORT=3902
volumes:
- qbittorrent-config:/config
- ./downloads/:/downloads
deploy:
resources:
limits:
memory: 0.5g # try to prevent mem leak
peerbanhelper:
image: ghostchu/peerbanhelper
restart: unless-stopped
container_name: qbittorrent-peerbanhelper
volumes:
- peerbanhelper-data:/app/data
ports:
- "3903:9898"
extra_hosts:
- "host.docker.internal:host-gateway" # allow to access services on host
environment:
- PUID=1000
- PGID=1000Then, log in to PeerBanHelper via localhost:3903 and configure the connection to qBittorrent. Since qBittorrent uses network_mode: host, the API address for PeerBanHelper is host.docker.internal:3902.
Leave all other settings as default.
Afterward, download any torrent and observe the memory usage.
Screenshot / Logs
Before downloading:
After downloading one anime episode, Debian's memory usage increased from 4.5GB to 4.65GB:
And it remains at 4.65GB:
Addition Information
This issue might be related to qBittorrent's WebUI memory leak, as detailed in https://github.com/qbittorrent/qBittorrent/issues/18830. A simple workaround is to log out and then log back in to release the session.
Hopefully, PeerBanHelper can also provide an option or feature to periodically log out and log back in to release the session.
Check list
- [X] I'm running the latest version of PBH that can be found in Github Releases
- [X] The downloaders that I've added already satisfied the requirements (E.g install plugins/adapters)
- [X] This is not a question/or the question is not listed in the README's FAQ or WIKI
- [X] I have not read these checkboxes and therefore I just ticked them all
- [X] This is not a security-related issue and can be safely reported in public
- [X] I know this issue may be closed without any warnings if I didn't fill the form correctly
Ghost-chu
bacon-cheeseburger
版本号 - Version
v6.0.1
操作系统平台和系统架构 - OS and CPU Arch
Debian 12, X86
部署方式 - Deploy method
官方Docker镜像
关联的下载器类型 - Downloader Type
qBittorrent
问题描述 - Issue Description
有好几次我发现qbittorrent在下载torrent的时候memory usage会不断上升直到整个Debian server都crash了。
后来通过问题https://github.com/qbittorrent/qBittorrent/issues/18830 得到启发，当把PeerBanHelper关掉后，qbittorrent的memory usage才开始趋于稳定。
复现步骤 - Reproduce steps
使用以下docker compose文件启动可复现实例：
然后通过
localhost:3903登录PeerBanHelper，并设置好对qbittorrent的连接，因为qbittorrent有network_mode: host，所以对于PeerBanHelper来说host.docker.internal:3902是qbittorrent的API网址其他一切都保持默认设置
之后下载任意种子，观察内存使用。
截图/日志文件 - Screenshot / Logs
开始下载前：
下载了一集动漫之后Debian的内存占用从4.5G升到4.65G：
并一直保持在4.65G：
额外信息 - Addition Information
此问题可能跟qbittorrent的WebUI memory leak有关，详见https://github.com/qbittorrent/qBittorrent/issues/18830 workaround很简单，就是logout再login以释放session
希望PeerBanHelper也可以给个选项或加个功能可以时不时的logout再login以释放session
检查清单 - Check list