High CPU use, Deluge 1.2.0 Arch linux x86_64

[gard]

Hi!
I have Deluge 1.2.0 and start it in "non classical mode" and.. gtkUI (/usr/bin/deluge) loads my processor on 100 % after some operating time.. Deluge 1.1.9 worked normal, this problem i have only after update to 1.2.0, see:



I restart the program (gtkUI /usr/bin/deluge), but after some time it again loads the processor to 100% CPU usage.. It's a bug?

[Maroko]

Same problem: Deluge 1.2.0, Arch linux 32 bit, classic or daemoned doesn't matter. Problem is in GUI. It occurs especially when I click on Peers tab - in few moments Deluge uses whole CPU. When I close gui and connect back to daemon it works fine until I click on Peers...

[gard]

The program already put works normally (gtkUI) , I too pressed on pears, but it works, I continue to observe of program operation)

[mogreen]

same problem

Linux mo-pc 2.6.32-ARCH #1 SMP PREEMPT Tue Feb 9 14:46:08 UTC 2010 i686 Intel(R) Pentium(R) 4 CPU 3.20GHz GenuineIntel GNU/Linux

Core Version: 1.2.900-dev
libtorrent version: 0.15.0.0



deluge eats up all my cpu cycles!

[decay]

Hello

I would just like to confirm this problem on both an Arch Linux and a Gentoo system (deluge runs in daemon mode on the Gentoo box). Running strace on the gui's pid shows me something like endless polling. I can probably get a more accurate trace if required.

I hope this gets fixed soon.

Thanks

[catscratch]

I just got this problem on Arch when I upgraded libtorrent-rasterbar to 0.14.9-1, downgrading to the previous version (0.14.8-1) seems to have fixed the issue for me.

[decay]

I've never upgraded libtorrent. The problem occurs with:

Code: Select all

Core Version: 1.2.0
libtorrent version: 0.14.8.0

[catscratch]

I'm still getting high CPU usage (90%+) with the new 1.2.1 Deluge which requires libtorrent 0.14.9.0.

[andar]

Hello

I would just like to confirm this problem on both an Arch Linux and a Gentoo system (deluge runs in daemon mode on the Gentoo box). Running strace on the gui's pid shows me something like endless polling. I can probably get a more accurate trace if required.

I hope this gets fixed soon.

Thanks

Sounds like the PyGTK bug. If you open another process from within Deluge, you could get 100% cpu usage. This will be fixed in pygtk 2.18, I think.

[decay]

Sounds like the PyGTK bug. If you open another process from within Deluge, you could get 100% cpu usage. This will be fixed in pygtk 2.18, I think.

I think you are right. Downgrading PyGTK to the stable 2.14 version seems to have done the trick. Thank you.