Comment 26 for bug 1245666

Alright, that seems fair. I'd guess much like you guessed that the rest
came from failed connection attempts during that period where the network
was unavailable. Yes, Pidgin having one defunct process for DNS lookups is
totally normal (and honestly something we all wish they'd put in the damn
documentation).

On Wed, Apr 26, 2017 at 7:45 AM, Thomas A. F. Thorne <
<email address hidden>> wrote:

> It has been noted on the developer site for Pidgin that 1 defunct is
> normal for DNS lookups.
> https://developer.pidgin.im/ticket/15617#comment:11
>
> The rest I have seen might come from failed attempts to connect to chat
> services. https://developer.pidgin.im/ticket/15617#comment:13 mentions
> you get one for every connect attempt. I did have a network issue last
> night that would have blocked IPv4 access for several hours. That might
> explain what i have seen. If I get further defunct processes without
> any signs of network disruption I will report back, else assume that it
> is provoked by network issues.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1245666
>
> Title:
> Pidgin is creating zombies
>
> Status in Pidgin:
> Unknown
> Status in pidgin package in Ubuntu:
> Confirmed
> Status in pidgin package in Fedora:
> Unknown
>
> Bug description:
> After upgrading to Kubuntu 13.10 pidgin is constantly creating new
> zombies.
>
> E.g. after an uptime of roughly 4 hours:
> $ ps aux | grep Z
> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
> cm 2589 0.0 0.0 0 0 ? Z 17:46 0:00
> [pidgin] <defunct>
> cm 3045 0.0 0.0 0 0 ? Z 17:47 0:00
> [pidgin] <defunct>
> cm 3106 0.0 0.0 0 0 ? Z 17:48 0:00
> [pidgin] <defunct>
> cm 3236 0.0 0.0 0 0 ? Z 17:50 0:00
> [pidgin] <defunct>
> cm 5760 0.0 0.0 0 0 ? Z 17:54 0:00
> [pidgin] <defunct>
> cm 5788 0.0 0.0 0 0 ? Z 18:02 0:00
> [pidgin] <defunct>
> cm 6405 0.0 0.0 0 0 ? Z 18:12 0:00
> [pidgin] <defunct>
> cm 6501 0.0 0.0 0 0 ? Z 18:22 0:00
> [pidgin] <defunct>
> cm 6519 0.0 0.0 0 0 ? Z 18:32 0:00
> [pidgin] <defunct>
> cm 6543 0.0 0.0 0 0 ? Z 18:42 0:00
> [pidgin] <defunct>
> cm 6580 0.0 0.0 0 0 ? Z 18:52 0:00
> [pidgin] <defunct>
> cm 6619 0.0 0.0 0 0 ? Z 19:02 0:00
> [pidgin] <defunct>
> cm 6645 0.0 0.0 0 0 ? Z 19:12 0:00
> [pidgin] <defunct>
> cm 6672 0.0 0.0 0 0 ? Z 19:22 0:00
> [pidgin] <defunct>
> cm 6691 0.0 0.0 0 0 ? Z 19:32 0:00
> [pidgin] <defunct>
> cm 6757 0.0 0.0 0 0 ? Z 19:42 0:00
> [pidgin] <defunct>
> cm 6846 0.0 0.0 0 0 ? Z 19:52 0:00
> [pidgin] <defunct>
> cm 6869 0.0 0.0 0 0 ? Z 20:01 0:00
> [pidgin] <defunct>
> cm 6889 0.0 0.0 0 0 ? Z 20:11 0:00
> [pidgin] <defunct>
> cm 6914 0.0 0.0 0 0 ? Z 20:21 0:00
> [pidgin] <defunct>
> cm 6931 0.0 0.0 0 0 ? Z 20:31 0:00
> [pidgin] <defunct>
> cm 6948 0.0 0.0 0 0 ? Z 20:41 0:00
> [pidgin] <defunct>
> cm 6972 0.0 0.0 0 0 ? Z 20:51 0:00
> [pidgin] <defunct>
> cm 6992 0.0 0.0 0 0 ? Z 21:01 0:00
> [pidgin] <defunct>
> cm 7015 0.0 0.0 0 0 ? Z 21:11 0:00
> [pidgin] <defunct>
> cm 7036 0.0 0.0 0 0 ? Z 21:20 0:00
> [pidgin] <defunct>
> cm 7121 0.0 0.0 0 0 ? Z 21:30 0:00
> [pidgin] <defunct>
> cm 7223 0.0 0.0 10984 940 pts/0 S+ 21:38 0:00 grep
> --color=auto Z
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/pidgin/+bug/1245666/+subscriptions
>