Opened 11 years ago

Closed 10 years ago

#6324 closed defect (out of date)

2.4.2 and 2.4.3 hang 99+% cpu usage on XP Pro

Reported by: mikedgreene Owned by: datallah
Milestone: Component: winpidgin (gtk)
Version: 2.4.3 Keywords: Hang infinte windows xp
Cc:

Description

After about 30-40 seconds, Pidgin begins to utilize nearly 100% cpu. Windows XP service pack 2.

I access Yahoo (3 times), AIM, and IRC.

I ran pidgin.exe from cygwin and collected the debug out put (twice): pidgin.exe -d > infinte.txt

Also I was able to open the debug window before it lost control, and the last line of the debug window matches the last line of both log files.

NOTE: On the second file, I did not touch the gui at all.

Attachments (2)

infinte.log (246.8 KB) - added by mikedgreene 11 years ago.
debug log from 100% cpu utilization
infinte-2.log (212.5 KB) - added by mikedgreene 11 years ago.
Second log file

Download all attachments as: .zip

Change History (9)

Changed 11 years ago by mikedgreene

debug log from 100% cpu utilization

Changed 11 years ago by mikedgreene

Second log file

comment:1 Changed 11 years ago by datallah

  • pending changed from 0 to 1

There's nothing particularly weird in the log files. When did this behavior start (and can you think of anything you might have changed around that time)?

comment:2 Changed 11 years ago by mikedgreene

  • pending changed from 1 to 0

I upgrade from 2.4.1 to either 2.4.2 or .3 and start pidgin.

It does not happen on 2.4.1. At this time that is what I am running. I re-install 2.4.1 to get back to a working environment.

I'm using this at work at Nortel. So I'm reasonably up to date on windows patches.

comment:3 Changed 11 years ago by mikedgreene

If there is a different debug level, or setting I can use, I will be happy to try that for data collection.

comment:4 Changed 11 years ago by eperez

Could you test with latest pidgin version?

Please disable all accounts and cycle over all the accounts, enabling one account at a time, to see if this is a problem specific to a protocol. If it happens with every protocol let us also know.

comment:5 Changed 10 years ago by mikedgreene

I upgraded to 2.4.5 I think and it stopped happening. I am currently on 2.5.2 and is still not happening.

Sorry I forgot to update the ticket.

comment:6 Changed 10 years ago by eperez

Could you please close this ticket and reopen if it ever happens again?

comment:7 Changed 10 years ago by deryni

  • Resolution set to out of date
  • Status changed from new to closed
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!