BT throttling the CPU

Bug #55439 reported by Andrew Conkling
2
Affects Status Importance Assigned to Milestone
bittornado (Ubuntu)
Invalid
Undecided
Unassigned
bittorrent (Ubuntu)
Invalid
Undecided
Unassigned
freeloader (Ubuntu)
Invalid
Undecided
Unassigned
gnome-btdownload (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: bittorrent

All the Python BitTorrent clients--bittorrent, gnome-btdownload, bittornado, and freeloader--throttle my CPU on Dapper. I was thinking it was a general problem with BT, but I subsequently tried Azureus, which has no problems, even when using twice the torrents.

It seems that this might be a problem with Python (since Azureus is excepted), or with something that each of these clients have in common. I have not tried any BT clients other than these five.

I can reproduce this when downloading or seeding any of the Ubuntu CD images.

Related thread: http://ubuntuforums.org/showthread.php?t=226076

Let me know if I can provide more and/or more specific information.

Revision history for this message
Marco Rodrigues (gothicx) wrote :

Thanks for your bug report. Could you please try to obtain a
strace by following the instructions on
       http://wiki.ubuntu.com/DebuggingProgramCrash.
This will greatly aid us in tracking down your problem.

Please look in /var/crash for a crash report on openoffice if you dont see one than please try to obtain an strace.

Revision history for this message
Marco Rodrigues (gothicx) wrote :

Ups.. not openoffice but bittornado.

Revision history for this message
Andrew Conkling (andrewski) wrote :

None of these programs is crashing; they are simply using a lot of CPU.

I'll check them on Feisty. Maybe it was an upstream bug that's been fixed since I reported it. (Note to self: check Deluge also.)

Revision history for this message
Andrew Conkling (andrewski) wrote :

I have only been able to check gnome-btdownload, but it's working fine right now.

Changed in gnome-btdownload:
status: Unconfirmed → Fix Released
Revision history for this message
Roberto Sarrionandia (rbs-tito) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in freeloader:
status: New → Invalid
Changed in bittorrent:
status: New → Invalid
Changed in bittornado:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.