irc: periodic '/who' polling causes connection drops
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Pidgin |
Fix Released
|
Unknown
|
|||
pidgin (Ubuntu) |
Fix Released
|
Medium
|
Mathieu Trudel-Lapierre |
Bug Description
After upgrading from 11.04 to 11.10, I found that pidgin was frequently (~20x/day) losing its connection to an IRC server. Other users on the channels I'm in reported I was disconnected with a 'Max SendQ exceeded' message. Pidgin reported simply 'Connection reset by peer'.
After a bit of debugging I found that recent versions of Pidgin now send a periodic '/who' for all channels the client is connected to. If you're in a lot of channels, or the channels have a lot of people in them (or both!), the server's send buffer can fill up resulting in the client being kicked.
The attached patch works around the problem by disabling the periodic /who altogether. I think a more correct fix would put a delay in irc_who_
Bug is present in pidgin 1:2.10.0-0ubuntu1; it is a regression from 1:2.7.11-1ubuntu2 in 11.04.
Related branches
Changed in pidgin (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Mathieu Trudel-Lapierre (mathieu-tl) |
Changed in pidgin: | |
status: | Unknown → New |
Changed in pidgin: | |
status: | Unknown → New |
Changed in pidgin: | |
status: | Unknown → Fix Released |
The attachment "irc_disable_ periodic_ who.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.
[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]