[Deluge] #3423: Memory Leak on Linux
Deluge
----------------------------+-------------------
Reporter: cinderblock | Type: bug
Status: new | Priority: major
Milestone: needs verified | Component: Core
Version: 2.0.3 | Keywords:
----------------------------+-------------------
I've been running Deluged 2.0.3 on my server for a while now. I have
nearly 500 torrents seeding but only a few active at a time. It's mostly
stable, except every ~month I take a look and it's using 100% of available
memory (32GB) and CPU.
Restarting the service brings the memory usage back down to ~400MB.
However it starts growing pretty quickly. I restarted my current instance
a day or two ago and it's currently using nearly 5GB. I just did a quick
test and looked at the RSS memory usage across a 10 minute interval. It
seems to be growing at 182 kBps. (At this rate it should only take 2 days
to fill all 32GB! So clearly this 10min sample doesn't capture the whole
picture...)
I have a nearly identical instance of Deluged running on the same machine
for a separate network. It only runs ~50 torrents and never seems to have
these memory leak problems.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3423>
Deluge <https://deluge-torrent.org/>
Deluge Project
Deluge
Reporter: cinderblock | Owner:
Type: bug | Status: new
Priority: major | Milestone: needs verified
Component: Core | Version: 2.0.3
--------------------------+----------------------------
Comment (by cinderblock):
I think this is actually a duplicate of #3327. I found some logs spewing
out many "Unhandled error in Deferred"s that match what is described
there.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3423#comment:1>
Deluge
Reporter: cinderblock | Owner:
Type: bug | Status: new
Priority: major | Milestone: needs verified
Component: Core | Version: 2.0.3
--------------------------+----------------------------
Comment (by Alexey104):
This is the libtorrent issue which was finally fixed in 1.2.10:
https://github.com/qbittorrent/qBittorrent/issues/12326
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3423#comment:2>
Deluge
Reporter: cinderblock | Owner:
Type: bug | Status: new
Priority: major | Milestone: needs verified
Component: Core | Version: 2.0.3
--------------------------+----------------------------
Comment (by cinderblock):
Glad to hear. What's it going to take for this to be incorporated to
Deluge? Should I be able to update to latest libtorrent, reinstall deluge
python3 bindings, and have it work?
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3423#comment:3>
Deluge
Reporter: cinderblock | Owner:
Type: bug | Status: new
Priority: major | Milestone: needs verified
Component: Core | Version: 2.0.3
--------------------------+----------------------------
Comment (by Alexey104):
Yes, just compile libtorrent with python bindings using the latest commit
from 1.2(not 2.0!) branch(if your distro doesn't already provide it in the
official repos), and it should solve your problem. I had been experiencing
exactly the same issue that you describe, and 1.2.10 completely solved it
for me.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3423#comment:4>
Deluge
Reporter: cinderblock | Owner:
Type: bug | Status: pending
Priority: major | Milestone: not applicable
Component: libtorrent | Version: 2.0.3
Resolution: | Keywords:
--------------------------+----------------------------
Changes (by Cas):
* status: new => pending
* component: Core => libtorrent
* milestone: needs verified => not applicable
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3423#comment:5>