Hacker News Reader

Comment by lynguist | Hacker News Reader

Qbittorrent unfortunately turned into a buggy mess and has no leadership. The github has hundreds of known issues that are not addressed. No qbittorrent client works reliably on Windows or Mac for at least a year or two. It gets hung up scanning downloaded torrents etc.

View on HN

I ran into the scanning bug. Turned out to be because I was leeching and had a max upload of 1kbps. I bumped that up to something more sensible and it started working again. This is an issue with most Torrent clients, although QBittorrent is definitely the worst with it that I've encountered. Unsure if it's what you're running into, but figured I'd point it out since it took me weeks to troubleshoot.

I run 5+ instances of qBittorrent on my unraid server and have not experienced any of these issues, same on macOS.

This really bums me out to hear. I have used many torrent clients over the years, Azureus -> uTorrent -> Deluge -> (transmission on mac and linux, although it didnt work great on Windows), until finally landing on qBittorrent and loving it.

I hope they figure out their maintainer issues.

qbittorrent on Linux has a crazy memory leak that makes it use more than 1gb of memory very fast and possibly. I had to stop using it for quite a few months. I refonwloaded it recently and it wasn't fixed.

I found out that's just disk cache. Try launching some memory hungry programs and you'll see the cache released and qBittorrent running at around 150 MB again.

Didn't know about that, thanks for the heads up.

Seems to work OK on my Pi with the web interface.

Reply on news.ycombinator.com