Opened 12 years ago

Closed 10 years ago

Last modified 10 years ago

#746 closed defect (out of date)

100% CPU usage while file transfer in progress (yahoo)

Reported by: andrixnet Owned by: datallah
Milestone: Component: Yahoo!/Yahoo! JAPAN
Version: 2.0 Keywords:
Cc:

Description

The subject says pretty much everything.

I got slugish system response while transfering a large file (4M) through Yahoo account. Transfer rate was about 30k/s. I popup up the CPU window and got >99% usage by pidgin.

Change History (7)

comment:1 Changed 12 years ago by lschiere

  • Milestone set to 3.0.0

comment:2 Changed 12 years ago by jkohen

I reported the same when using IRC on the sf.net tracker a long time ago. I was doing local transfers between two clients and a server, all running on the same host. One client was X-Chat and it was preforming nicely, but Gaim was taking all CPU.

comment:3 Changed 11 years ago by datallah

  • Milestone 3.0.0 deleted
  • pending changed from 0 to 1

I haven't ever been able to recreate this.

comment:4 Changed 11 years ago by andrixnet

  • pending changed from 1 to 0

Since Yahoo transfer mostly doesn't work, I haven't tried it again recently.

When I'll get some new info, I'll get back. Need to find a buddy with which file transfer works at least in one of the directions...

comment:5 Changed 10 years ago by bernmeister

It's been a while...is this still an issue?

comment:6 Changed 10 years ago by darkrain42

  • Component changed from winpidgin (gtk) to Yahoo!
  • Resolution set to out of date
  • Status changed from new to closed

There have been a lot of changes in the yahoo! prpl, especially in Pidgin 2.6.0. If you're still experiencing this issue with it when it's released, please comment here and we'll re-open the ticket (or file a new one).

comment:7 Changed 10 years ago by andrixnet

Just tested a few file transfer between Pidgin and yahoo client 8 and 9. Several megs each file, CPU usage for pidgin below 30% (well, below 10% most of the time).

Tried at transfer rates between 50k and 2000k.

Leaving as closed. Thank you.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!