12
qbittorrent has decided to use all the memory, what do I do? (lemmy.dbzer0.com)
submitted 4 days ago by to c/qbittorrent@lemmy.dbzer0.com
13 comments fedilink hide all child comments
 

Every time I open qbittorrent it slowly more and more memory util it runs out.

Does that happen to someone else?

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 4 days ago* (4 children)

Every time I open qbittorrent it slowly more and more memory util it runs out.

Does anything happen after that, or is this just an observation? Your OS should know when to swap to disk to avoid things like crashes, etc.

You may want to update your post with more information on your OS, setup, if you're actively uploading/download torrents, how many torrents you're seeding, things like that.

When I was on Windows I do remember seeing qBittorrent/Libtorrent 2.x use as much available RAM as it could but nothing bad ever happened, I just ignored it. In fact at one point the qBittorrent devs even added an option to limit RAM use and I used to just set that to the maximum RAM & just let qBittorrent/Libtorrent do its thing. Not sure if the Windows version of qBittorrent still has that option but it used to be a setting under Tools/Preferences/Advanced at the top under the qBittorrent section. I don't see it in the current version under Linux.

Barring any special settings the usual advice would be to limit your maximum connections and/or upload/download bandwidth, probably tweaking the Global Maximum Connections will be enough. The more connections qBittorrent/Libtorrent establishes the more RAM gets used. Libtorrent 2.x historically used to use more RAM but I don't know nowadays how much of a problem that is.

In case it helps I haven't seen anything abnormal on qBittorrent 5.3.0/Libtorrent 2.x + Debian Linux.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 2 points 4 days ago (3 children)

    Until it closes and pops up a notification telling me that the OS prevented it from running out of memory. After that I can't start qbittorrent again until after a reboot.

    I don't know, I will probably try some other distro next week.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 4 days ago* (2 children)

    Interesting, you might be running into an actual bug that may need to be fixed. There's mention of something similar over in the qBittorrent Github issues e.g.

    https://github.com/qbittorrent/qBittorrent/issues/25202

    That particular bug report mentions Debian, same as me, but I haven't run into it so am not sure what triggers the issue. But my Debian installation has an updated Linux Kernel so I wonder if that has something to do with it.. I'm on 7.2.11, Debian Stable is on 6.12 I believe. Just out of curiousity do you know which Linux kernel version you're on? In terminal just run

    uname -a

    To potentially work around the issue, if it's just something with the latest qBittorrent, you could try downgrading to an earlier version. I've never used Bazzite but I assume it allows you to run AppImage binaries - You can grab earlier version qBittorrent .appimage binaries from their Sourceforge page linked at https://www.qbittorrent.org/download (after download you'd need to chmod +x the .appimage file to actually be able to execute it).

    Barring all that, lowering your maximum connections / bandwidth could be worth a try since that should lower the overall RAM requirements for qBittorrent/Libtorrent at runtime.

    PS - Back up your qBittorrent settings folders before any downgrades/upgrades

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 4 days ago (1 child)

    Kernel version: 7.2.15-ogc1.1.fc45.x86_64 (64-bit)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 4 days ago*

    Ugh I guess we can rule out the Linux Kernel version, at least we know that's not the issue.

    I'm not familiar with Bazzite but I think(?) it grabs and updates apps through Flathub (per https://docs.bazzite.gg/Installing_and_Managing_Software/Flatpak/) so another idea is trying the qBittorrent appimage from the qBittorrent devs, instead of the version that qBittorrent binary Bazzite gives you, just to test & see if there is any difference. That should at least rule out some specific issue with the qBittorrent binary in Flathub. (In theory it should work the same)

    Might be out of ideas beyond that :/ You can try posting in qBittorrent's Github, maybe it's the same bug some other people are running into.

  • permalink
  • fedilink
  • source
  • parent