I’ve recently upgraded to Growl 2.0 and was pleased to see an item in the
change log saying “resolves the high CPU issue”.
Unfortunately, that doesn’t seem to be the case. I’ve just hit the bug
again. Here’s my details:
- Growl 2.0
- OS X 10.7.5
- 13" late 2011 MBP
- The following Growl-enabled applications were running at the time when
the bug occurred:
* Adium
* Dropbox
* Mail (GrowlMail)
* iTerm2
* Quicksilver
* Skype
* Spotify
* Twitter
Unfortunately it didn’t occur to me to sample the process before killing it
(I can do that next time, if it helps diagnosing the problem). However,
I’ve found the following Growl-related message in the Console:
> 31/10/2012 07:40:19.878 Adium: <GrowlGNTPNotificationAttempt:
0x10ac4d420> failed because Error Domain=NSPOSIXErrorDomain Code=61
"Connection refused" UserInfo=0x10fb0dd80
{NSLocalizedDescription=Connection refused, NSLocalizedFailureReason=Error
in connect() function}
(I’ve got the same error twice, two minutes apart)
… however, I’m not sure whether this was just prior to Growl’s screwup or
just after I killed it.
--
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/-/a69faSmPWYgJ.
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.
