Ok, just had the issue with the 100% CPU usage by Growl and here's the connections list before I quit Skype:
roman@Romans-MacBook-Pro-2:~/Aconex/deployment/field $ lsof -i :23053 | cut -d' ' -f1 | sort | uniq -c 1 COMMAND 2 Google 242 Growl 216 Skype and after: roman@Romans-MacBook-Pro-2:~/Aconex/deployment/field $ lsof -i :23053 | cut -d' ' -f1 | sort | uniq -c 1 COMMAND 2 Google 63 Growl However Growl died almost straight away after I quit Skype. On Mon, Apr 2, 2012 at 8:02 AM, Eduardo Habkost <[email protected]>wrote: > It looks like the issue is not specific to Adium, but to the configuration > I used for Adium. I managed to isolate specific cases where connections are > kept open. > > - In one test, I configured Adium to send "connect" Growl notifications, > and they were enabled. The socket was closed by Adium just after the > notification response was received. > > - In another test, I kept the same configuration on Adium, but disabled > the notification Growl preferences. The socket was kept open after the > error response from Growl. I don't know if the client was supposed to close > the socket, or Growl should have closed it. > > In case it helps the developers, a Wireshark capture file showing both > cases is available at: > http://dl.dropbox.com/u/1626365/adium-two-notifications.pcap > > -- > Eduardo > > > On Sunday, April 1, 2012 at 17:38 , Chris Forsythe wrote: > > > That's a symptom of the problem. However it seems that the real problem > is that the connections are not dying, resulting in a too many files open > type scenario. We've been working on a fix for this and it's really one of > the last few things blocking 1.4. > > > > -- > > Chris Forsythe > > > > > > On Sunday, April 1, 2012 at 7:00 AM, Eduardo Habkost wrote: > > > > > Maybe Skype has a similar bug. To find out if it has the same issue, > check the output of the following command on the terminal: > > > > > > lsof -i :23053 | cut -d' ' -f1 | sort | uniq -c > > > > > > It should show how many sockets to Growl are open by each application. > If you see hundreds of open connections when Growl starts eating CPU, it is > probably the same bug. > > > > > > -- > > > Eduardo > > > > > > > > > On Sunday, April 1, 2012 at 03:23 , Roman Revyakin wrote: > > > > > > > Hi Eduardo, > > > > > > > > Thanks for your email, that sheds a bit of light on the problem > indeed. If 100% CPU Growl usage is caused by the same reason of too many > open files it is definitely not Adium, as I am not running it here. > > > > I run Skype though which is sending its notifications through Growl. > > > > > > > > Regards, > > > > Roman > > > > > > > > On Sun, Apr 1, 2012 at 3:44 AM, Eduardo Habkost > > > > <[email protected](mailto: > [email protected]) (mailto:[email protected])> wrote: > > > > > Adding more information to my previous message (I can't reply to > my own message as it seems to be stuck on the moderation queue): > > > > > > > > > > I just found out what caused the "Too many open files" error: my > Growl process has 287 open files according to 'lsof'. 247 of them are TCP > sockets. And 246 of them are connections from Adium! The default ulimit set > by Mac OS X Lion seems to be 256 open files. > > > > > > > > > > Right now Adium has 246 established TCP sockets to Growl, and 600 > SYN_SENT sockets trying to connect to Growl. (!) > > > > > > > > > > I'm using Adium 1.5. > > > > > > > > > > So, the question for all other people seeing this problem: are you > using Adium, too? > > > > > > > > > > > > > > > On Monday, February 27, 2012 6:08:26 PM UTC-3, Christopher > Forsythe wrote: > > > > > > We also need to know any steps that you were taking at the time. > The big problem is that no one on the team can reproduce the majority of > the CPU issues. Samples can help, but can only tell us so much. > > > > > > > > > > > > Chris > > > > > -- > > > > > You received this message because you are subscribed to the Google > Groups "Growl Discuss" group. > > > > > To view this discussion on the web visit > https://groups.google.com/d/msg/growldiscuss/-/SRuU3EtQGgEJ. > > > > > > > > > > To post to this group, send email to > > > > > [email protected](mailto: > [email protected]) (mailto:[email protected]). > > > > > To unsubscribe from this group, send email to > [email protected] (mailto: > [email protected]) (mailto: > growldiscuss%[email protected] (mailto: > [email protected])). > > > > > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. > > > > > > > > > > > > > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > Groups "Growl Discuss" group. > > > > To post to this group, send email to > > > > [email protected](mailto: > [email protected]) (mailto:[email protected]). > > > > To unsubscribe from this group, send email to > [email protected] (mailto: > [email protected]) (mailto: > [email protected]). > > > > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. > > > > > > > > > > > > > > > > > > -- > > > You received this message because you are subscribed to the Google > Groups "Growl Discuss" group. > > > To post to this group, send email to [email protected](mailto: > [email protected]). > > > To unsubscribe from this group, send email to > [email protected] (mailto: > [email protected]). > > > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. > > > > > > > > -- > > You received this message because you are subscribed to the Google > Groups "Growl Discuss" group. > > To post to this group, send email to [email protected](mailto: > [email protected]). > > To unsubscribe from this group, send email to > [email protected] (mailto: > [email protected]). > > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
