|

»

Pidgin (Old Gaim)

»

Pidgin - Tracker

#10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c.

View: New views

15 Messages — Rating Filter: Alert me

	#10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. ------------------+--------------------------------------------------------- Reporter: jsled \| Type: defect Status: new \| Component: pidgin (gtk) Version: 2.6.3 \| Keywords: ------------------+--------------------------------------------------------- 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@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@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@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> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #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@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@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@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@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@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@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 _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by darkrain42): * status: new => pending Comment: What account types do you have enabled? What plugins are you using? -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:2> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by jsled): * status: pending => new Comment: Replying to [comment:2 darkrain42]: > What account types do you have enabled? What plugins are you using? Accounts: * XMPP [redacted]@gmail.com, enabled * XMPP alert@... (via dreamhost), disabled * XMPP [redacted]@im.sun.com, disabled * XMPP jsled@... (via dreamhost), enabled * AIM, enabled Plugins enabled: * XMPP Console (unused by me) At present the same process (started yesterday) has 465 "socket" files open (via lsof, grep, &c.) (Thanks for the re-formatting, QuLogic. :) -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:3> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #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: \| --------------------+------------------------------------------------------- Comment(by jsled): sigh Accounts: * XMPP [redacted]@gmail.com, enabled * XMPP alert@… (via dreamhost), disabled * XMPP [redacted]@im.sun.com, disabled * XMPP jsled@… (via dreamhost), enabled * AIM, enabled Plugins enabled: * XMPP Console (unused by me) -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:4> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by darkrain42): * status: new => pending Comment: Could you run `lsof -p $(pidof pidgin) -i` and attach the output of that, please? -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:5> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: darkrain42 Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by darkrain42): * owner: => darkrain42 -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:6> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: darkrain42 Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Comment(by darkrain42): Replying to [comment:5 darkrain42]: > Could you run `lsof -p $(pidof pidgin) -i` and attach the output of that, please? Apparently the PID selector doesn't work when -i is also specified (at least on my system), so you can add a "\| grep pidgin" in there, instead. -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:7> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: darkrain42 Type: defect \| Status: new Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by jsled): * status: pending => new -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:8#comment:> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: darkrain42 Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by darkrain42): * status: new => pending Comment: What sound method are you using? If you disable all sounds (or use an external command), does the leak stop? Are you using PulseAudio? If so, what version? -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:10> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: darkrain42 Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by jsled): * status: pending => new Comment: Sound Method=Automatic, which I'd guess is alsa; no PA here, yet. I'll disable sounds and give it a go. -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:11> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: darkrain42 Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by darkrain42): * status: new => pending -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:12> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: darkrain42 Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by jsled): * status: pending => new Comment: Disabling sounds seems to be working well :) jsled@phoenix [~]$ lsof -p $(ps auxwwf \|grep "pidgin" \|grep -v grep \| awk '{ print $2 }') \|grep "socket" \| wc -l 5 That's after ~4 days of uptime (since the timestamp of my #comment11). Clearly this helps me out and I don't want pidgin to make noise anyways, but hopefully it helps track down the problem. Let me know if it'd help to rebuild with instrumented source, run in gdb, &c. -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:13> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: darkrain42 Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by darkrain42): * status: new => pending Comment: This is likely to be an issue with the gstreamer output method in-use. There was an issue with exactly these symptoms (the gstreamer !PulseAudio plugin leaked a thread and some fds for each sound played). if you open up gstreamer-properties (part of gnome-media), what is the default output method in it? -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:14> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker
	Re: #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. by Pidgin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message #10727: pidgin leaks sockets, stops logging, opening urls, connecting, &c. --------------------+------------------------------------------------------- Reporter: jsled \| Owner: darkrain42 Type: defect \| Status: pending Milestone: \| Component: pidgin (gtk) Version: 2.6.3 \| Resolution: Keywords: \| --------------------+------------------------------------------------------- Changes (by jsled): * status: pending => new Comment: Plugin: ALSA, Device: Default, Pipeline: alsasink. -- Ticket URL: <http://developer.pidgin.im/ticket/10727#comment:15> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker