[Pidgin] #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c.
Pidgin
trac at pidgin.im
Thu Nov 12 20:50:11 EST 2009
#10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c.
--------------------+-------------------------------------------------------
Reporter: jsled | Owner:
Type: defect | Status: new
Milestone: | Component: pidgin (gtk)
Version: 2.6.3 | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Description changed by QuLogic:
Old description:
> For a number of minor release versions, now, I've been running into
> situations where pidgin will start misbehaving after days of uptime.
>
> - New conversations will result in messages <paraphrase>"logging failed
> for this conversation"</paraphrase>.
>
> - Clicking on urls in chats will result in <paraphrase>xdg-open failure:
> no more resources</paraphrase>
>
> - Reconnection failures to various xmpp networks (gmail, dreamhost-ed
> jabber).
>
> I don't have compelling evidence, except looking at the following just
> before restarting pidgin, just now:
>
> before restart:
>
> jsled at phoenix [~]$ lsof -p 31527 |grep "socket" | wc -l
> 1003
>
> e.g.:
>
> pidgin 31527 jsled 987u unix 0xffff8800b0c85b80 0t0 15171547
> socket
> pidgin 31527 jsled 988u unix 0xffff88003954a680 0t0 15171643
> socket
> pidgin 31527 jsled 989u unix 0xffff88003954b700 0t0 15171644
> socket
> pidgin 31527 jsled 990u unix 0xffff88003954a3c0 0t0 15171645
> socket
> pidgin 31527 jsled 991u unix 0xffff880039549b80 0t0 15171646
> socket
> pidgin 31527 jsled 992u unix 0xffff88003954a100 0t0 15171647
> socket
> pidgin 31527 jsled 993u unix 0xffff880065df1080 0t0 15171648
> socket
> pidgin 31527 jsled 994u unix 0xffff8800b0c842c0 0t0 15175093
> socket
> pidgin 31527 jsled 995u unix 0xffff8800b0c863c0 0t0 15175094
> socket
> pidgin 31527 jsled 996u unix 0xffff8800b0c879c0 0t0 15175095
> socket
> pidgin 31527 jsled 997u unix 0xffff8800b0c84580 0t0 15175096
> socket
> pidgin 31527 jsled 998u unix 0xffff880065df1b80 0t0 15183959
> socket
> pidgin 31527 jsled 999u unix 0xffff880065df23c0 0t0 15183960
> socket
> pidgin 31527 jsled 1000u unix 0xffff880065df1600 0t0 15183961
> socket
> pidgin 31527 jsled 1001u unix 0xffff880065df0dc0 0t0 15183962
> socket
> pidgin 31527 jsled 1002u unix 0xffff880065f2db80 0t0 15184028
> socket
> pidgin 31527 jsled 1003u unix 0xffff880065f2ec00 0t0 15184029
> socket
> pidgin 31527 jsled 1004u unix 0xffff8800394c1600 0t0 15184030
> socket
> pidgin 31527 jsled 1005u unix 0xffff8800394c2100 0t0 15184031
> socket
> pidgin 31527 jsled 1006u unix 0xffff88009d573180 0t0 15184063
> socket
> pidgin 31527 jsled 1007u unix 0xffff88009d572c00 0t0 15184064
> socket
> pidgin 31527 jsled 1008u unix 0xffff88009ba99b80 0t0 15184065
> socket
> pidgin 31527 jsled 1009u unix 0xffff88001f578000 0t0 15184066
> socket
> pidgin 31527 jsled 1010u unix 0xffff88001f5782c0 0t0 15184067
> socket
> pidgin 31527 jsled 1011u unix 0xffff88001f578580 0t0 15184068
> socket
> pidgin 31527 jsled 1012u unix 0xffff88001f57a680 0t0 15194109
> socket
> pidgin 31527 jsled 1013u unix 0xffff88001f57a3c0 0t0 15194110
> socket
> pidgin 31527 jsled 1014u unix 0xffff88001f579e40 0t0 15194111
> socket
> pidgin 31527 jsled 1015u unix 0xffff88001f57a100 0t0 15194112
> socket
> pidgin 31527 jsled 1016u unix 0xffff88001f579340 0t0 15194113
> socket
> pidgin 31527 jsled 1017u unix 0xffff88001f579600 0t0 15194114
> socket
> pidgin 31527 jsled 1018u unix 0xffff8800b0c85e40 0t0 15194146
> socket
> pidgin 31527 jsled 1019u unix 0xffff8800b0c84b00 0t0 15194147
> socket
> pidgin 31527 jsled 1020u unix 0xffff8800b0c86680 0t0 15194148
> socket
> pidgin 31527 jsled 1021u unix 0xffff8800b0c85080 0t0 15194149
> socket
> pidgin 31527 jsled 1022u unix 0xffff8800b0c85600 0t0 15194150
> socket
> pidgin 31527 jsled 1023u unix 0xffff88001dbac000 0t0 15194151
> socket
>
> after restart:
>
> jsled at phoenix [~]$ lsof -p $(ps axuwwf |grep "pidgin" |grep -v "grep" |
> awk '{ print $2 }') |grep "socket" | wc -l
> 11
>
> Sorry it's not a very well-formed bug report, but please let me know
> if/what to capture the next time I encounter the problem. It's reliably
> repeatable, but on a long time span (5+ days).
>
> jsled at phoenix [~]$ uname -a
> Linux phoenix 2.6.28-gentoo-r5 #7 SMP PREEMPT Thu May 14 22:59:05 EDT
> 2009 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AuthenticAMD
> GNU/Linux
>
> Installed versions: 2.6.3(03:47:43 PM 10/22/2009)(dbus doc
> gstreamer gtk idn ncurses nls perl spell -bonjour -debug -eds -gadu
> -gnutls -groupwise -meanwhile -networkmanager -prediction -qq -sasl -silc
> -tcl -tk -zephyr)
>
> But I've been seeing this presently with 2.6.3, but I believe I saw it
> with both 2.5.8 and 2.5.9 at least, as well.
New description:
For a number of minor release versions, now, I've been running into
situations where pidgin will start misbehaving after days of uptime.
- New conversations will result in messages <paraphrase>"logging failed
for this conversation"</paraphrase>.
- Clicking on urls in chats will result in <paraphrase>xdg-open failure:
no more resources</paraphrase>
- Reconnection failures to various xmpp networks (gmail, dreamhost-ed
jabber).
I don't have compelling evidence, except looking at the following just
before restarting pidgin, just now:
before restart:
{{{
jsled at phoenix [~]$ lsof -p 31527 |grep "socket" | wc -l
1003
e.g.:
pidgin 31527 jsled 987u unix 0xffff8800b0c85b80 0t0 15171547
socket
pidgin 31527 jsled 988u unix 0xffff88003954a680 0t0 15171643
socket
pidgin 31527 jsled 989u unix 0xffff88003954b700 0t0 15171644
socket
pidgin 31527 jsled 990u unix 0xffff88003954a3c0 0t0 15171645
socket
pidgin 31527 jsled 991u unix 0xffff880039549b80 0t0 15171646
socket
pidgin 31527 jsled 992u unix 0xffff88003954a100 0t0 15171647
socket
pidgin 31527 jsled 993u unix 0xffff880065df1080 0t0 15171648
socket
pidgin 31527 jsled 994u unix 0xffff8800b0c842c0 0t0 15175093
socket
pidgin 31527 jsled 995u unix 0xffff8800b0c863c0 0t0 15175094
socket
pidgin 31527 jsled 996u unix 0xffff8800b0c879c0 0t0 15175095
socket
pidgin 31527 jsled 997u unix 0xffff8800b0c84580 0t0 15175096
socket
pidgin 31527 jsled 998u unix 0xffff880065df1b80 0t0 15183959
socket
pidgin 31527 jsled 999u unix 0xffff880065df23c0 0t0 15183960
socket
pidgin 31527 jsled 1000u unix 0xffff880065df1600 0t0 15183961
socket
pidgin 31527 jsled 1001u unix 0xffff880065df0dc0 0t0 15183962
socket
pidgin 31527 jsled 1002u unix 0xffff880065f2db80 0t0 15184028
socket
pidgin 31527 jsled 1003u unix 0xffff880065f2ec00 0t0 15184029
socket
pidgin 31527 jsled 1004u unix 0xffff8800394c1600 0t0 15184030
socket
pidgin 31527 jsled 1005u unix 0xffff8800394c2100 0t0 15184031
socket
pidgin 31527 jsled 1006u unix 0xffff88009d573180 0t0 15184063
socket
pidgin 31527 jsled 1007u unix 0xffff88009d572c00 0t0 15184064
socket
pidgin 31527 jsled 1008u unix 0xffff88009ba99b80 0t0 15184065
socket
pidgin 31527 jsled 1009u unix 0xffff88001f578000 0t0 15184066
socket
pidgin 31527 jsled 1010u unix 0xffff88001f5782c0 0t0 15184067
socket
pidgin 31527 jsled 1011u unix 0xffff88001f578580 0t0 15184068
socket
pidgin 31527 jsled 1012u unix 0xffff88001f57a680 0t0 15194109
socket
pidgin 31527 jsled 1013u unix 0xffff88001f57a3c0 0t0 15194110
socket
pidgin 31527 jsled 1014u unix 0xffff88001f579e40 0t0 15194111
socket
pidgin 31527 jsled 1015u unix 0xffff88001f57a100 0t0 15194112
socket
pidgin 31527 jsled 1016u unix 0xffff88001f579340 0t0 15194113
socket
pidgin 31527 jsled 1017u unix 0xffff88001f579600 0t0 15194114
socket
pidgin 31527 jsled 1018u unix 0xffff8800b0c85e40 0t0 15194146
socket
pidgin 31527 jsled 1019u unix 0xffff8800b0c84b00 0t0 15194147
socket
pidgin 31527 jsled 1020u unix 0xffff8800b0c86680 0t0 15194148
socket
pidgin 31527 jsled 1021u unix 0xffff8800b0c85080 0t0 15194149
socket
pidgin 31527 jsled 1022u unix 0xffff8800b0c85600 0t0 15194150
socket
pidgin 31527 jsled 1023u unix 0xffff88001dbac000 0t0 15194151
socket
}}}
after restart:
{{{
jsled at phoenix [~]$ lsof -p $(ps axuwwf |grep "pidgin" |grep -v "grep" |
awk '{ print $2 }') |grep "socket" | wc -l
11
}}}
Sorry it's not a very well-formed bug report, but please let me know
if/what to capture the next time I encounter the problem. It's reliably
repeatable, but on a long time span (5+ days).
{{{
jsled at phoenix [~]$ uname -a
Linux phoenix 2.6.28-gentoo-r5 #7 SMP PREEMPT Thu May 14 22:59:05 EDT 2009
x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AuthenticAMD
GNU/Linux
Installed versions: 2.6.3(03:47:43 PM 10/22/2009)(dbus doc gstreamer
gtk idn ncurses nls perl spell -bonjour -debug -eds -gadu -gnutls
-groupwise -meanwhile -networkmanager -prediction -qq -sasl -silc -tcl -tk
-zephyr)
}}}
But I've been seeing this presently with 2.6.3, but I believe I saw it
with both 2.5.8 and 2.5.9 at least, as well.
--
--
Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:1>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list