[Pidgin] #14262: High CPU usage (~100%) on giantic channels

Pidgin trac at pidgin.im
Wed Jun 8 13:28:19 EDT 2011


#14262: High CPU usage (~100%) on giantic channels
-------------------+--------------------------------------------------------
Reporter:  ethail  |        Type:  defect   
  Status:  new     |   Component:  libpurple
 Version:  2.8.0   |    Keywords:           
-------------------+--------------------------------------------------------
 As a consecuence of updating from pidgin 2.7.11 to 2.8.0 on a 64 bits
 linux 2.6.38 machine with Intel Pentium T4300 (2 cores 2.10GHz) there have
 been suffered high cpu ussage spikes when joining and randomly when
 staying at giantic channels like #archlinux (~1050) and #ubuntu (~1600)
 (joined #ubuntu as a test to confirm #archlinux was not the problem).

 This behaviour does not happen with channels that have less population
 like #pidgin (~170 when tested) and did not happen on 2.7.11.

 This is the output of the debugging window when joining the channels said
 before:

 #archlinux

 (18:51:21) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:51:21) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:51:21) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:51:22) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:51:23) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:51:24) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:51:24) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:51:24) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:51:25) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 #ubuntu

 (18:53:16) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:53:17) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:53:17) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:53:17) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!

 (18:53:19) dbus: Invalid UTF-8 string passed to signal, emitting salvaged
 string!



 In addition to the high CPU usage and random spikes, the time used to join
 high populated channels has increased between 2 and 4 times what used to
 be on 2.7.11

-- 
Ticket URL: <http://developer.pidgin.im/ticket/14262>
Pidgin <http://pidgin.im>
Pidgin


More information about the Tracker mailing list