Opened 14 years ago

Closed 13 years ago

Last modified 9 years ago

#1888 closed bug (Invalid)

100% cpu usage at seeding

Reported by: jone Owned by:
Priority: major Milestone:
Component: Core Version: 1.3.2
Keywords: Cc:

Description

After a complete download torrent, at seeding (50-60 Kbps!) cpu loading increases to 100%.

Attachments (2)

deluge.log.txt.zip (26.9 KB ) - added by jone 14 years ago.
Log file
Sys. Monitor- Deluge.png (82.8 KB ) - added by jone 14 years ago.
Network and CPU usage screenshot

Download all attachments as: .zip

Change History (10)

comment:1 by Calum, 14 years ago

What is at 100% cpu? Need a lot more info than you have provided. http://forum.deluge-torrent.org/viewtopic.php?f=7&t=31035

by jone, 14 years ago

Attachment: deluge.log.txt.zip added

Log file

by jone, 14 years ago

Attachment: Sys. Monitor- Deluge.png added

Network and CPU usage screenshot

comment:2 by jone, 14 years ago

Deluge loads CPU on 100%

OS: i686 Linux (OpenSUSE 11.4)

deluge-1.3.2-19.2.noarch libtorrent-rasterbar6-0.15.6-2.1.i586 python-libtorrent-rasterbar-0.15.6-2.1.i586

Plugins: enabled (Blocklist, Notifications, Execute) UI: GTK Filesystem: ext4 Package type: rpm

comment:3 by andar, 14 years ago

What are you doing in the Execute plugin? Could it be a script you're running post-download thats causing the issue?

in reply to:  3 comment:4 by jone, 14 years ago

Replying to andar:

What are you doing in the Execute plugin? Could it be a script you're running post-download thats causing the issue?

Execute: notify-send message only.

comment:5 by Calum, 14 years ago

Is this reproducable? If so can you test with Deluge in server/client mode (non-classic) and see if it is deluge-gtk or deluged using the cpu.

The most likely thing I can think of is a known pygtk bug that will cause 100% cpu when opening files from within Deluge see #1396

comment:6 by Calum, 14 years ago

Status: newpending

comment:7 by Calum, 13 years ago

Resolution: invalid
Status: pendingclosed

comment:8 by Calum, 9 years ago

Milestone: 1.3.x

Milestone deleted

Note: See TracTickets for help on using tickets.