deluge uses 100%+ of CPU when using full allocation

I've seen that libtorrent has had an upgrade to address a memory leak but I am not convinced this issue has been fully resolved.

I am not experiencing a memory leak but my deluge is consuming far too many resources (CPU) for it to be "normal". It is as high as 65% which is was never the case before installing Maverick and Deluge 1.3.0

I am also seeing 100% CPU usage from deluge, sometimes. This only started after I upgraded to Maverick. This CPU drain keeps going even after I pause all the torrents, so it's very clearly a bug. The `top` command shows that the CPU load is 50% user/ 50% system. Quitting deluge, of course, brings this down to 2% / 2%.

I am also experiencing this in Ubuntu 10.10 x64
Deluge Core Version: 1.3.1
libtorrent version: 0.15.4.0

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
18659 nvilppu 20 0 638m 123m 24m R 102 3.1 2:35.69 /usr/bin/deluge

I too was experiencing this issue on Ubuntu 10.10 x86_64 running Deluge 1.3.1.

After a few google searches, I discovered that my issue was related to the "Open Folder" option in the torrent context menu. Full details here: http://dev.deluge-torrent.org/ticket/1396

I've stopped using that option 2 weeks ago and I haven't experienced this issue since.

I also noticed Deluge uses too much CPU ressources (70 or 80%)
Deluge version 1.3.0
libtorrent version: 0.15.4.0
Ubuntu maverick x86-64

Linux desktop 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux

I also have this problem.

I have same problem. Deluge use my CPU 50% every time. (AMD dual core)

This happens to me as well. Deluge would randomly shoot up to 100% of one of my cores, even with no active torrents, but after restarting it, it will go back to 0% CPU.

Got the same problem. deluge-gtk quickly reaches 100% CPU activity on Mint 10 Julia 64-bit (kernel 2.6.35-22-generic, single core). It does this even if there's no torrent active.

CPU reaches 100% when you open a downloaded file, or even just view it in Nautilus in 'Icons' mode, while deluge is running.
I guess that in Nautilus it is caused by the 'preview' feature (which has to open the file).