pidgin uses all idle CPU time, and frequent lock ups if gtalk password is incorrect

[LGB [Gábor Lénárt]]

Pidgin (1:2.4.3-0ubuntu1~hardy1) in Ubuntu 8.04.1 (32 bit) went totally unusable now. Even with idle computer (not much disk I/O or any other CPU sensitive application running) it uses all of the idle CPU, and only showing empty windows (like when there is no window refresh works). Sometimes it goes back for some minutes than it out of order for even half an hour or so. So in the view point of usage it can't be used for anything now. According to "strace -p <pid>", it does this:

gettimeofday({1216981502, 879951}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=10, events=POLLIN|POLLPRI}, {fd=18, events=POLLIN}, {fd=16, events=POLLIN}, {fd=38, events=POLLIN}, {fd=6, events=POLLIN}, {fd=14, events=POLLIN}, {fd=19, events=POLLIN}, {fd=17, events=POLLIN}, {fd=36, events=POLLIN}, {fd=37, events=POLLIN}, {fd=45, events=POLLIN, revents=POLLIN|POLLERR|POLLHUP}], 13, 0) = 1
recv(45, "", 5, 0) = 0
read(3, 0x8130bd4, 4096) = -1 EAGAIN (Resource temporarily unavailable)

in an endless loop. There were similar bug reports before, but now it is almost a constant problem not allow pidgin to be used more than some seconds ... I don't know which upgrade made things even worse than before, because I was on vacation for a long time not upgrading things for a while.

Sometimes it's even not possible to simply kill pidgin with "kill" command, just with signal 9.

[LGB [Gábor Lénárt] (lgb)]

Sorry, I've just realized that it is maybe because of my modified password on gmail.com, it seems the problem is caused when pidgin tries to connect to gmail.com. Though, I think it is still a bug, because it should be reported as wrong password or something and not with a behaviour like the one I've reported. Pidgin sometimes reported "read error", instead of wrong password.

Should I modify my bug report to reflect the change of my problem?

[Magnus S (magnuss)]

Hi, pidgin should never use all cpu, so there is a bug somewhere. Is this bug still reproducible? If so, please attach a backtrace (https://wiki.ubuntu.com/Backtrace) to this bug report.
Also tell us which version of pidgin and ubuntu you are using now.

Thanks.
//magnus

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.