Hello all, For some reason this has been happening much less frequently the last couple of weeks. But I did see this just a few minutes ago. The UI gets complete frozen, but it does continue to update itself when I pull a chat window to the forground from behind another window. It prints out no new messages or does not accept input. I cant even select contacts in the buddy list.
I dont know how long pidgin had been frozen but I did start trying to debug. I first attached a strace to the process: [ra@hamburger ~]$ ps -ef | grep pidgin ra 2694 2267 0 01:14 ? 00:05:53 pidgin [ra@hamburger ~]$ strace -p 2694 Process 2694 attached sendto(19, "\241h\366\223\272\251\21\23\255\26l9\370p\255\300\214\376\322y\221k\341\3507\16\202\200}~%\301"... , 679, 0, NULL, 0) = -1 EAGAIN (Resource temporarily unavailable) sendto(19, "\241h\366\223\272\251\21\23\255\26l9\370p\255\300\214\376\322y\221k\341\3507\16\202\200}~%\301"... , 679, 0, NULL, 0) = -1 EAGAIN (Resource temporarily unavailable) sendto(19, "\241h\366\223\272\251\21\23\255\26l9\370p\255\300\214\376\322y\221k\341\3507\16\202\200}~%\301"... , 679, 0, NULL, 0) = -1 EAGAIN (Resource temporarily unavailable) sendto(19, "\241h\366\223\272\251\21\23\255\26l9\370p\255\300\214\376\322y\221k\341\3507\16\202\200}~%\301"... , 679, 0, NULL, 0) = -1 EAGAIN (Resource temporarily unavailable) sendto(19, "\241h\366\223\272\251\21\23\255\26l9\370p\255\300\214\376\322y\221k\341\3507\16\202\200}~%\301"... , 679, 0, NULL, 0) = -1 EAGAIN (Resource temporarily unavailable) sendto(19, "\241h\366\223\272\251\21\23\255\26l9\370p\255\300\214\376\322y\221k\341\3507\16\202\200}~%\301"... , 679, 0, NULL, 0) = -1 EAGAIN (Resource temporarily unavailable) sendto(19, "\241h\366\223\272\251\21\23\255\26l9\370p\255\300\214\376\322y\221k\341\3507\16\202\200}~%\301"... , 679, 0, NULL, 0) = -1 EAGAIN (Resource temporarily unavailable) sendto(19, "\241h\366\223\272\251\21\23\255\26l9\370p\255\300\214\376\322y\221k\341\3507\16\202\200}~%\301"... , 679, 0, NULL, 0) = -1 EAGAIN (Resource temporarily unavailable) Huge, endless list of that.. [ra@hamburger ~]$ ll /proc/2694/fd/19 l-wx------. 1 ra ra 64 May 11 01:14 /proc/2694/fd/19 -> /home/ra/.purple/logs/sipe/r...@ok.is%2cok%5cra/.system/2013-05-11.125047+0000GMT.txt I then tried to attach gdb to the process but gdb told me I needed the debuginfo packages (I'm a Fedora user) so I disconnected gdb and installed the needed packages. This is where a miracle happened. pidgin recovered from the infinite loop and proceeded working as normal. I am however ready to hook up gdb the next time this happens. -- Rikki ----- Original Message ----- From: "Ethan Blanton" <e...@pidgin.im> To: "Matthias Apitz" <g...@unixarea.de> Cc: support@pidgin.im Sent: Thursday, 18 April, 2013 2:29:13 PM Subject: Re: pidgin and VPN issues. Matthias Apitz spake unto us the following wisdom: > IMHO this sounds like established TCP connections are terminated by the > VPN down/change and some layer in pidgin is waiting (for ever) for a > response. One could watch with TCPDUMP if this is true. All of our network I/O should be nonblocking, and thus should not affect the UI. This is more likely a logic bug of some kind, as Mark noted. Ethan _______________________________________________ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support _______________________________________________ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
