Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#14262 closed defect (fixed)

High CPU usage (~100%) on giantic channels

Reported by: ethail Owned by:
Milestone: 2.9.0 Component: libpurple
Version: 2.8.0 Keywords:
Cc:

Description

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

Change History (5)

comment:1 Changed 5 years ago by BW~Merlin

I am having the same issue (random high cpu usage spikes) on Windows Vista Ultimate SP2 x64 after updating from 2.7.11 to 2.8.0

comment:2 follow-up: Changed 5 years ago by deryni

  • Status changed from new to pending

Is that all the debug window output that shows up when this happens?

comment:3 in reply to: ↑ 2 Changed 5 years ago by ethail

  • Status changed from pending to new

Replying to deryni:

Is that all the debug window output that shows up when this happens?

When the cpu spikes happen, that's all the output. Also, there is the common output when joining a channel, whether or not the cpu usage increases to nearly 100%:

(I have changed my user on the computer by the word "user" on the paths)

(14:28:28) util: Writing file blist.xml to directory /home/user/.purple

(14:28:28) util: Writing file /home/user/.purple/blist.xml

(14:28:30) util: Writing file prefs.xml to directory /home/user/.purple

(14:28:30) util: Writing file /home/user/.purple/prefs.xml

As said, this output appears on every joined channel, with or without the high cpu usage.

comment:4 Changed 5 years ago by BW~Merlin

Pidgin 2.9.0 fixes this problem for the most part but I am still seeing CPU spikes.

comment:5 Changed 5 years ago by deryni

  • Milestone set to 2.9.0
  • Resolution set to fixed
  • Status changed from new to closed

I'm closing this ticket as fixed because it is almost certainly the IRC large room bug.

BW~Merlin: You are seeing CPU spikes when exactly? If this isn't resolved by this fix it sounds like something else might be going on for you in which case that will probably want a new ticket.

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!