Pidgin 2.4.1 (Hardy): proper closed connection handling patch from upstream
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pidgin (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: pidgin
the following patch needs to be brought in from upstream to fix "Pidgin uses 100% CPU" problem on hardy:
it appears to cause at least the following bug:
https:/
and a number of other complaints where pidgin gets stuck in a loop reading from a closed socket.
my strace looks something like:
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=10, events=
read(16, "", 4095) = 0
read(3, 0x812ebd4, 4096) = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday(
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=10, events=
read(16, "", 4095) = 0
read(3, 0x812ebd4, 4096) = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday(
here's a relevant discussion on pidgin developer list:
http://
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
In this specific case, what do w need to do to trigger Pidgin's 100% CPU usage? This will help us to find and resolve the problem.