deluged memory leak

[bfx81@…]

After quite time deluged reachs "suspicious" memory size. (see below, 470MB in 9hrs...) :p

• No deluge clients was connected to the server for the whole time (neither web)
• Trying to force a recheck of a file didn't work
• SIG_TERM only shutdown the server but leave the process active with his files open.
• In this hanged state memory grows seems stopped.

compiled with gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.1) Python 2.5.2 librtorrent included in deluged-1.0.4 tarball used boost-1.34.1

---

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7729 bluefox 20 0 829m 471m 9428 S 0.0 25.0 9:32.94 deluged

-- other related system information Portage 2.1.4.5 (default-linux/amd64/2007.0/desktop, gcc-4.1.2, glibc-2.6.1-r0, 2.6.24-gentoo-r8 x86_64) ================================================================= System uname: 2.6.24-gentoo-r8 x86_64 AMD Athlon(tm) 64 Processor 3200+ Timestamp of tree: Fri, 07 Nov 2008 06:38:01 +0000 app-shells/bash: 3.2_p33 dev-java/java-config: 1.3.7, 2.1.6 dev-lang/python: 2.4.4-r14, 2.5.2-r7 dev-python/pycrypto: 2.0.1-r6 dev-util/cmake: 2.4.6-r1 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r2 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3

[anonymous]

preview missed... sorry...