Growl 1.3.1 massive CPU-usage

[dereinevogelda]

I'm using Growl 1.3.1 on OS X 10.7.2 and Safari 5.1.1.
After a while Growl increases CPU-usage for now up to 150% on a 2011
MacBook Pro 13" with Core i5 Dual Core CPU. If i stop Growl via kill
or Activity monitor and restart it, it works fine for several days
again.

As i read this group partial this is happening several times to other
Growl-users.

Regards
Mark

[Michal Cichra]

Same here with Growl 1.3.2.

On 25 lis, 12:38, dereinevogelda <dereinevoge...@googlemail.com>
wrote:

[Chris Forsythe]

We've been trying to reproduce this so that we could debug it, but so far we have no steps to reproduce the issue. Which makes debugging this… rather difficult.

We have a ticket on it with about 10 samples on it, but if you could sample the process as well that'd be a huge help.

Chris

> --
> You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
> To post to this group, send email to growld...@googlegroups.com.
> To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
>

[Michael Shick]

I have the same problem here, on 1.3.2. It's normally the sort of thing where I come in in the morning and find my MacBook Air's fans spinning full blast.

I've attached all the Growl related messages in the Console, from a known state of Growl being fine, to my killing the process.

Here are some examples:

12/14/11 8:42:12.290 AM Skype: <GrowlGNTPNotificationAttempt: 0x155819d0> failed because Error Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out" UserInfo=0x14068e60 {NSLocalizedDescription=Read operation timed out}

12/14/11 8:42:36.025 AM Growl: Core Data: annotation: -executeRequest: encountered exception = Updating max pk failed:  with userInfo = {

    NSSQLiteErrorDomain = 14;

}

12/14/11 8:42:36.128 AM Growl: Core Data: annotation: -executeRequest: encountered exception = Updating max pk failed:  with userInfo = {

    NSSQLiteErrorDomain = 14;

}

[Chris George]

Adding my own sample as it happened to me (after it had previously crashed).

[jeffrey wishnie]

This is still happening with me on 1.3.2 .

I've already posted a sample.

This happens consistently whenever Growl is left running for a few
hours—100% reproducible, though there are NO specific steps other than
"launch growl, leave computer running"

One additional bit of info: when I look at the process list in iStats
Menu "launchd" is the process taking all the CPU. Activity monitor
still shows the "Growl" as the process taking all the CPU.

This has become completely unusable—I've uninstalled Growl 1.3.2 and
reverted to 1.2.2 :-(

[Michael Shick]

I just had a 100% CPU usage event. Here's my sample.

[Stewf]

I continue to experience this in 1.3.2. I've posted a sample above but
here are some Consule errors at the time of high CPU usage:

12/22/11 6:41:12.541 PM Growl: ERROR: could not read template '/Users/
~/Library/Application Support/Growl/Plugins/Mono.growlStyle/Contents/
Resources/template.html' - Error Domain=NSCocoaErrorDomain Code=256
"The operation couldn’t be completed. (Cocoa error 256.)"
UserInfo=0x7fdc1632f4f0 {NSFilePath=/Users/~/Library/Application
Support/Growl/Plugins/Mono.growlStyle/Contents/Resources/
template.html, NSUnderlyingError=0x7fdc1631ce10 "The operation
couldn’t be completed. Too many open files"}
12/22/11 6:41:12.541 PM Growl: -[NSView setPolicyDelegate:]:
unrecognized selector sent to instance 0x7fdc16329060
12/22/11 6:41:12.542 PM Growl: -[NSView setPolicyDelegate:]:
unrecognized selector sent to instance 0x7fdc16329060
12/22/11 6:41:12.647 PM Growl: (
0 CoreFoundation 0x00007fff920f7286
__exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff91f74d5e
objc_exception_throw + 43
2 CoreFoundation 0x00007fff921834ce -[NSObject
doesNotRecognizeSelector:] + 190
3 CoreFoundation 0x00007fff920e4133
___forwarding___ + 371
4 CoreFoundation 0x00007fff920e3f48
_CF_forwarding_prep_0 + 232
5 Growl 0x000000010aa7d053 -
[GrowlWebKitWindowController dealloc] + 67
6 AppKit 0x00007fff87621633 -
[NSWindowController release] + 159
7 Growl 0x000000010aa7c8e6 -
[GrowlWebKitWindowController initWithBridge:] + 218
8 Growl 0x000000010aa89c39 -
[GrowlNotificationDisplayBridge makeWindowControllers] + 99
9 Growl 0x000000010aa89589 -
[GrowlDisplayPlugin displayNotification:] + 212
10 Growl 0x000000010aa81dae -
[GrowlApplicationController dispatchNotificationWithDictionary:] +
1924
11 CoreFoundation 0x00007fff920e6a1d -[NSObject
performSelector:withObject:] + 61
12 Foundation 0x00007fff90591e44
__NSThreadPerformPerform + 214
13 CoreFoundation 0x00007fff92065b51
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
14 CoreFoundation 0x00007fff920653bd
__CFRunLoopDoSources0 + 253
15 CoreFoundation 0x00007fff9208c1a9
__CFRunLoopRun + 905
16 CoreFoundation 0x00007fff9208bae6
CFRunLoopRunSpecific + 230
17 HIToolbox 0x00007fff8fed43d3
RunCurrentEventLoopInMode + 277
18 HIToolbox 0x00007fff8fedb63d
ReceiveNextEventCommon + 355
19 HIToolbox 0x00007fff8fedb4ca
BlockUntilNextEventMatchingListInMode + 62
20 AppKit 0x00007fff875fa3f1
_DPSNextEvent + 659
21 AppKit 0x00007fff875f9cf5 -
[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
22 AppKit 0x00007fff875f662d -
[NSApplication run] + 470
23 Growl 0x000000010aa8c7a9 -
[GrowlApplication run] + 182
24 AppKit 0x00007fff8787580c
NSApplicationMain + 867
25 Growl 0x000000010aa748a5 main + 134
26 Growl 0x000000010aa69bc4 start + 52
)


12/22/11 6:42:36.124 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:42:36.125 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:42:36.226 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:42:39.227 PM Growl: Unresolved error Error
Domain=NSCocoaErrorDomain Code=134030 "The operation couldn’t be
completed. (Cocoa error 134030.)" UserInfo=0x7fdc1634b5b0
{NSSQLiteErrorDomain=14, NSUnderlyingException=Updating max pk
failed: }, {
NSSQLiteErrorDomain = 14;
NSUnderlyingException = "Updating max pk failed: ";
}


12/22/11 6:51:40.489 PM Growl: ERROR: could not read template '(null)'
- Error Domain=NSCocoaErrorDomain Code=258 "The operation couldn’t be
completed. (Cocoa error 258.)" UserInfo=0x10ac17e00 {}
12/22/11 6:51:40.489 PM Growl: -[NSView setPolicyDelegate:]:
unrecognized selector sent to instance 0x7fdc188a1c40
12/22/11 6:51:40.489 PM Growl: -[NSView setPolicyDelegate:]:
unrecognized selector sent to instance 0x7fdc188a1c40


12/22/11 6:53:32.326 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:53:32.326 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:53:32.427 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:53:35.429 PM Growl: Unresolved error Error
Domain=NSCocoaErrorDomain Code=134030 "The operation couldn’t be
completed. (Cocoa error 134030.)" UserInfo=0x7fdc18894660
{NSSQLiteErrorDomain=14, NSUnderlyingException=Updating max pk
failed: }, {
NSSQLiteErrorDomain = 14;
NSUnderlyingException = "Updating max pk failed: ";
}
12/22/11 6:53:35.568 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:53:35.568 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:53:35.670 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:53:38.671 PM Growl: Unresolved error Error
Domain=NSCocoaErrorDomain Code=134030 "The operation couldn’t be
completed. (Cocoa error 134030.)" UserInfo=0x7fdc1647ff40
{NSSQLiteErrorDomain=14, NSUnderlyingException=Updating max pk
failed: }, {
NSSQLiteErrorDomain = 14;
NSUnderlyingException = "Updating max pk failed: ";
}
12/22/11 6:53:38.696 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:53:38.696 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:53:38.797 PM Growl: Core Data: annotation: -executeRequest:

encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}

12/22/11 6:53:41.799 PM Growl: Unresolved error Error
Domain=NSCocoaErrorDomain Code=134030 "The operation couldn’t be
completed. (Cocoa error 134030.)" UserInfo=0x7fdc135f49e0
{NSSQLiteErrorDomain=14, NSUnderlyingException=Updating max pk
failed: }, {
NSSQLiteErrorDomain = 14;
NSUnderlyingException = "Updating max pk failed: ";
}

[Chris Forsythe]

Can you resend this log as an file instead of inline? 

-- 
Chris Forsythe

[HFTobeason]

Not sure if my example applies, or will help, but Growl was sucking
100%+ this AM. I clicked the menu bar icon, and Growl crashed. I
have pertinent console log info and a crash log, if someone could let
me know how/where to send them.

[Chris Forsythe]

If you email, just attach the files like a regular email. If you use the web interface, it's probably easier to use a service like dropbox to share the files.

A crash log would definitely help, but also if you can get a Sample with Activity Monitor that'd be great too. We're going to be working on a 1.3.3 to try to knock some of these cpu issues out, so anything you can gather would be great.

-- 
Chris Forsythe

[John Dyer]

Any idea when 1.3.3 will be out? Really sucks that Growl seems to
CONSTANTLY consume pretty much all the CPU on my system... Seems also
like its a systemic problem with just about everyone thats using
it....

thanks, and appreciate your hard work to help resolve this.

-John

[Christopher Forsythe]

The problem hasn't been resolved yet, so no not yet.

Chris

[Roman]

Same here: occasionally Growl would start burning CPU like hell (100%) on my MacBook Pro 17". Growl is of the latest version (1.3.2), Lion 10.7.2 with all the latest updates installed, excerpt from the log file with Growl messages in it attached.

Skype's Growl core was updated to 1.3.1 using the Growl Version detective. 

[Michael Tsai]

I'm seeing this as well. Sample attached. If I quit Growl while it's using lots of CPU, it crashes.

--Michael

[Dan Payne]

I'm having the same issue as well. I suspected it was the Hardware Growler so I disabled that but to no avail. I'll post a sample next time it happens.

[yksk]

After I uninstalled SIMBL, my Growl (1.3.3) looks fine.

[Sarah Alawami]

I don't have that piece of software in my case.  any other suggestions? I don't see what could be conflicting with the growl to cause it to use over 80 percent of my cpu. I have the sample file linked if you guys want it.

Take care.

On Jan 31, 2012, at 2:54 AM, yksk wrote:

After I uninstalled SIMBL, my Growl (1.3.3) looks fine.

--
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/-/erll5kvm3SEJ.

[Алексей Селезнев]

The same problem for Growl 1.3.3 on MacBook Pro 13, i5, 8Gb RAM. Huge CPU overload every day (110 - 150%). It can be solved by Growl reload but it's no way in my oppinion. 

[Sarah Alawami]

Ah I also have a 13 inch 4 gigs of ram. if I even load growl once I am in trouble. Please please have this fixed! If you need to see my sampling I'll pull it up again.

On Jan 31, 2012, at 9:30 PM, Алексей Селезнев wrote:

The same problem for Growl 1.3.3 on MacBook Pro 13, i5, 8Gb RAM. Huge CPU overload every day (110 - 150%). It can be solved by Growl reload but it's no way in my oppinion. 

--
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/-/q3NLawvd8PYJ.

[Charlie S]

Has any one tried different styles?

--


----
Charlie Schloss

Grab Opera the fastest browser on earth @
http://my.opera.com/community/download.pl?ref=Chas4&p=opera_desktop


Why Open the Web?

Despite the connecting purpose of the Web, it is not entirely open to all of
its users. When used correctly, HTML documents can be displayed across
platforms and devices. However, many devices are excluded access to Web
content.

http://my.opera.com/community/openweb/info/

[Sarah Alawami]

The only style I can try is speach as I'm a visually impaired user I cannot use anythign else. I believe the boxcar plugin did the same thing though.

Take care all.

[Roman]

Occured again today after upgrade to 1.3.3. Here are some samples attached.

[mikealex]

I'm having this problem with Growl 1.3.3. I don't have a sample file, but I have multiple crash logs.

MacBook Pro, 15-inch, Early 2011
2.3 GHz Intel Core 7
16GB 1333 MHz DDR3
AMD Radeon HD 6750M 1024MB
Mac OS X Lion 10.7.3 (11D50)

As others have said, steps to reproduce are just start Growl and leave the machine running for a while.

It seemed to start with mine after I installed HardwareGrowler. I disabled all of HardwareGrowler's power related messages in Growler, since it constantly reports "On A/C power" over and over. I'm going to disable HardwareGrowler and see if the problem still happens.

[Charlie S]

I did get the cpu spike but it did not last very long

--
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/-/RAh1YREa3KIJ.

To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.

[mikealex]

I shutdown HardwareGrowler immediately after posting my first message and left the machine running, including overnight. 12 hours with no problem.

[Sarah Alawami]

Yeah I don't have hardware growler.  and mine will spike until I quit growl. Not even a restart works. I even tried different themes. no speech of corse but it still spiked at 97 percent and once at 102 percent.

Take care all. and hope this can be fixed.

Sarah Alawami, owner and founder of WICS Radio America. Check us out on the web at http://wics.cc and thanks for tuning in.

On Feb 21, 2012, at 4:00 AM, mikealex wrote:

I shutdown HardwareGrowler immediately after posting my first message and left the machine running, including overnight. 12 hours with no problem.

--
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/-/KynseXQ5uzYJ.

[Roman Revyakin]

Here's another sample of the Growl-gone mad process. Now that I upgraded to 1.3.3 it happens on a regular basis. May I downgrade to 1.3.1 in any way? That version seemed a bit more stable with this regard.

[mikealex]

I still haven't had any problems since shutting down HardwareGrowler.

[Sarah Alawami]

lol. I don't have hardware growler. so I just shut down growl until it's fixed for good.

Take care all and be safe.

Sarah Alawami, owner and founder of WICS Radio America. Check us out on the web at http://wics.cc and thanks for tuning in.

On Feb 23, 2012, at 6:26 PM, mikealex wrote:

I still haven't had any problems since shutting down HardwareGrowler.

--
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/-/S1Fmtal68GIJ.

[Wevah]

Happening to me as well, every week or so. Not a dealbreaker, but
still annoying.

[Roman Revyakin]

Still happening after I shut down the Hardware Growler. Sample attached.

On Sun, Feb 26, 2012 at 8:39 AM, Wevah <thew...@gmail.com> wrote:

Happening to me as well, every week or so. Not a dealbreaker, but
still annoying.

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.

[Christopher Forsythe]

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

[Roman Revyakin]

Hi Chris,

I understand your need in reproducing the issue, however I cannot tell you the exact steps that lead to the eventual spike of the CPU usage by Growl.

Approximate order of events is: launch the Growl on a MacBook, let it running for a while there, closing and opening the lid from time to time and see eventually it eating up > 100% CPU time when the fans start spinning like crazy.

My environment is:

MacBook Pro 17" (late 2011), 8GB RAM

What's running and using Growl: Skype, Chrome, Evernote, iTerm ,gfxCardStatus, Dropbox (which I've just noticed I need to upgrade the FW still, done now)

Unfortunately, this is so much I can tell you. If you can think of any other information that could help you to investigate the issue, I am more than eager to help!

Thanks,

Best regards,

Roman

[Roman Revyakin]

All right Chris, I think I might have got some more info for you on that issue now that it has just happened again:

Just before Growl starting spinning my MacBook fans, there was a Google Hangout going with 8 people at the time and the Time Out 2 (which I did not mention in my last email as it did not use the Growl notifications) started to fade my screen in order to enforce a "normal" 10 minutes break. Simultaneously as the screen started fading, the fans started to spin really fast, so the actual spike might has happened a bit earlier.

I attach another sample to this email.

Thanks,

Regards,

Roman 

[domenic]

Chris, the following may help:

I'm running into the same CPU issue. After a few hours of "normal"
usage, cpu spikes to 100%+, force-quitting and restarting fixes it for
a while.

I use Skype chats extensively. Text-only, never video.
I am running a self-compiled version of Growl (not app store).
I do not have any other programs sending Growl notifications.

The issue happens 3-4 times per workday. I can time them for you if it
would help.

Thanks,
-D

On Feb 27, 1:08 pm, Christopher Forsythe <ch...@growl.info> 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
>

> On Sun, Feb 26, 2012 at 8:09 PM, Roman Revyakin <roman....@googlemail.com>wrote:
>
>
>
>
>
>
>
> > Still happening after I shut down the Hardware Growler. Sample attached.
>

[Roman Revyakin]

Off-topic: with the new style of notifications coming in the Mac OS Mountain Lion just round the corner: 

http://www.apple.com/macosx/mountain-lion/features.html#notifications 

will Growl become redundant? 

[Chris Forsythe]

Please do not derail this thread with another topic.

-- 
Chris Forsythe

[Chris Forsythe]

Timing them couldn't hurt at this point. We've been narrowing things down, samples really aren't helping here. Which display styles are you folks who are seeing this using?

-- 
Chris Forsythe

[Sarah Alawami]

I'm using speach for mine.  I think someone was using smoke for there theme? but I'm not sure.

[Roman Revyakin]

Hi Chris,

I'm using SnowBezel.

Roman

[Wevah]

I'm using Black Glass (by Ryan Collins). I was using Mono (by
Cristopher Lobay) before; I don't recall having this issue with that
theme. Could be a red herring, though…

[Chris Forsythe]

Ya, I'm more concerned that it's the webkit plugin or not. Both of those are webkit.

-- 
Chris Forsythe

[John Dyer]

Who do I contact about getting my money back ?  Seems no one give a two shits about this issue and all we get is "send more samples"  My guess is they are waiting until 10.8 comes out w/ notification center and growl becomes obsolete.  

[Sarah Alawami]

Actually they are working on it. I just got a message on this list about what is causing this and it should be ready by the time the next major release comes out if i understand the message correctly.

Take care all and be safe.

Sarah Alawami, owner and founder of WICS Radio America. Check us out on the web at http://wics.cc and thanks for tuning in.

On Mar 22, 2012, at 5:55 PM, John Dyer wrote:

Who do I contact about getting my money back ?  Seems no one give a two shits about this issue and all we get is "send more samples"  My guess is they are waiting until 10.8 comes out w/ notification center and growl becomes obsolete.  

--
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/-/4ctPxFOLfuQJ.

[Eduardo Habkost]

Hi,

Did you manage to find the root cause of this bug already? Maybe I can help collect more information. I built Growl from source and managed to attach a debugger to the Growl process that was eating 100% CPU.

I don't know how exactly to trigger the error. If I just leave my machine running Growl overnight (with some apps that generate notifications running), most times Growl is already using 100% CPU in the morning.

What I managed to find out until now is:

- There are two threads eating lots of CPU: _dispatch_mgr_thread and _dispatch_work_thread2.

- I don't see any Growl functions in the backtraces inside the _dispatch_mgr_thread, after collecting Time Profiler samples for ~1 minute using Instruments.

- Inside _dispatch_mgr_thread, the heaviest stack trace is inside [GCDAsyncSocket doAccept].

- After putting a breakpoint on doAccept, I noticed that accept() is returning error, errno is set to 24 (EMFILE, Too many open files)

So, it looks likes this is a sum of two bugs:

1) Somehow Growl is getting EMFILE errors, probably because of a bug somewhere else;

2) Once Growl start hitting EMFILE errors, it starts to eat 100% CPU.

I will hang out on the #growl IRC channel (nickname ehabkost), in case somebody wants to help to investigate this.

[Eduardo Habkost]

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:

[Roman Revyakin]

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 

--
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.

[mikealex]

I do use Adium, but I still have not seen the problem since I stopped using HardwareGrowler.
...Mike

[Eduardo Habkost]

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 <ehab...@gmail.com (mailto:ehab...@gmail.com)> 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 growld...@googlegroups.com (mailto:growld...@googlegroups.com).
> > To unsubscribe from this group, send email to growldiscuss...@googlegroups.com (mailto:growldiscuss%2Bunsu...@googlegroups.com).

> > 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 growld...@googlegroups.com (mailto:growld...@googlegroups.com).
> To unsubscribe from this group, send email to growldiscuss...@googlegroups.com (mailto:growldiscuss...@googlegroups.com).

[Chris Forsythe]

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

To post to this group, send email to growld...@googlegroups.com.

To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.

[Roman Revyakin]

Hi Eduardo,

Thanks for that handy command line, Growl is not eating 100% right now on my laptop, however I see there are many open connections open to Growl on behalf of Skype indeed: 

$ lsof -i :23053 | cut -d' ' -f1 | sort | uniq -c

   1 COMMAND

   1 Google

 180 Growl

 178 Skype

I wonder why the Growl Devs did not provide an update on the issue in that thread as it would seem from Chris's last message that they knew what the problem was.

Regards,

Roman

To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.

[Eduardo Habkost]

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

> > > > To post to this group, send email to growld...@googlegroups.com (mailto:growld...@googlegroups.com) (mailto:growld...@googlegroups.com).
> > > > To unsubscribe from this group, send email to growldiscuss...@googlegroups.com (mailto:growldiscuss...@googlegroups.com) (mailto:growldiscuss%2Bunsu...@googlegroups.com (mailto:2Bunsu...@googlegroups.com)).

> > > > 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 growld...@googlegroups.com (mailto:growld...@googlegroups.com) (mailto:growld...@googlegroups.com).
> > > To unsubscribe from this group, send email to growldiscuss...@googlegroups.com (mailto:growldiscuss...@googlegroups.com) (mailto:growldiscuss...@googlegroups.com).

[Roman Revyakin]

Ok, just had the issue with the 100% CPU usage by Growl and here's the connections list before I quit Skype:

$ lsof -i :23053 | cut -d' ' -f1 | sort | uniq -c

   1 COMMAND

   2 Google

 242 Growl

 216 Skype

and after: 

$ 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. 

To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.

[joelw135]

After starting GROWL new Beta I had using command lsof -i :23053 | cut

-d' ' -f1 | sort | uniq -c

1 Command
5 GROWL
After 1/2 hour it was
1 Command
14 GROWL

[Roman Revyakin]

Where does one download Growl Betas?
Do you use something like Skype or Adium which usually produce a lot of messages so that one can test the undying connections? 

[Eduardo Habkost]

Note that in the case of Adium, I have noticed the bug only because one notification type ("Contact signs on") was enabled on my Adium preferences, but disabled on my Growl preferences.

After I disabled the notification on Adium itself, I stopped seeing the bug. That happened because (on my case), connections were kept open only when Adium got "the user disabled this notification" error responses.

--
Eduardo

On Tuesday, April 3, 2012 at 19:11 , Roman Revyakin wrote:

> Where does one download Growl Betas?
> Do you use something like Skype or Adium which usually produce a lot of messages so that one can test the undying connections?
>

[Roman Revyakin]

In case of Skype, when I choose to use "Growl" notifications instead of "Built-in", all of its internal preferences for showing the notification become greyed out, so it is impossible to check or uncheck them.

I tried to bring inline the preferences and start running Skype again using Growl with no effect on the connections to Growl (after a while they accumulated to 165 again), so I am thinking of turning off Skype sending notifications through Growl, rather using the built-in notifier.

I will be definitely missing out on the Growl history, I know. 

Interestingly, I have had the "Contact becomes available" in Skype preferences disabled, but I noticed that once Growl dies, Skype begins to display those notifications through its own built-in Growl notifier. 

[Roman Revyakin]

And yeah, there are no notifications settings for "Contact comes online" inside Skype itself, and I was talking about those ones popping up whenever Growl dies, not the "Contact becomes available". 

They are in Growl preferences though and I have them disabled. 

So, in short - it might be the same problem as with Adium, only I cannot work around it.

[Roman Revyakin]

Update: if I set Growl to display the "... went online" "...went offline" notifications, then there is no connection leak on Growl side experienced any longer. 

[Roman Revyakin]

Found an advice in a separate thread to update my version of Skype:

https://groups.google.com/forum/?fromgroups#!topic/growldiscuss/ekGV6Striyo

 (somehow I assumed I would be notified of an update but I was not). Now running Skype version 5.6.0.203 (was 5.5.3.xx before) and do not see so far any constant increase in connections to Growl. Will see what happens when I leave it running for a while.

[Chris Forsythe]

The high cpu issue is something we're tracking down and working on fixing for 1.4. It's taken so long since we finally figured out the root cause very very recently. The fix is unfortunately going to take a bit longer, especially since we're doing additional testing to make sure that everything works right. The good news is now that we know the root cause, that's half the battle. :)

-- 
Chris Forsythe

[Eduardo Habkost]

Hi, Chris,

When it gets released, will the fix require updating the client framework on the apps, or just updating Growl?

--
Eduardo

[Roman Revyakin]

A small update from me: I was wrong about the fix of the issue by upgrading Skype to 5.6: after I updated the framework to Growl 1.3.1 in Skype, the undying connections came back again.

Chris, could you tell if there is any ETA on when the 1.4 gets released? 

[Roman Revyakin]

I downgraded Growl framework in Skype back to 1.2.3 and the connections issue was gone. I guess I'll leave it like that until the 1.4 comes out.

[Chris Forsythe]

We're hoping to have 1.4 out soon, but I don't have an exact date.

-- 
Chris Forsythe

[Stewf]

I have the CPU usage issue and I do not run Skype or Adium. My
overnight running apps are:

Dropbox
Hazel
iScrobbler
NetNewsWire
Twitter

It does not seem to be related to Notifications or the Scroll as the
problem occurs even when no notifications are sent.

On Mar 31, 7:44 pm, Eduardo Habkost <ehabk...@gmail.com> 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

[Robbie]

Has this issue been fixed for 1.4?

[Christopher Forsythe]

Unfortunately it has not. We had to put out the 1.4 update to get the fixes in before the sandboxing deadline, and to get the new start at login stuff in as well so that we could remove the older stuff from the startup list gracefully. The cpu issue is very complicated and essentially we ran out of time.

Chris

On Sat, Jun 23, 2012 at 5:58 PM, Robbie <robert...@gmail.com> wrote:

Has this issue been fixed for 1.4?

--

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/-/Uz9SW-3xASgJ.

To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.

--
Chris Forsythe

@The_Tick

[Daniel Siemer]

Hello all, thought I would stop in here and make sure that everyone
did know that we do know the cause of this bug, and are working
actively to fix it once and for all. Growl 2.0 will have the fix, it
is not done yet, but it has made very good progress so far, and I have
not seen the cause of this in my personal testing yet, and we will
work to keep you updated on when testing and such will begin.

On Jul 10, 2:51 pm, Nikolaj de Fine Licht <nikli...@gmail.com> wrote:
> Please let me know how I can help. I have the same issue with 1.4 on a 2.2
> GHz Core i7 15" MBPro running 10.7.4. It happens every 3-4 days, showing
> 130% CPU usage.
>
> Nikolaj

[Carsten]

Daniel, I know you guys are working on it, but it's been a while, and this is a pretty serious bug! Do you have any timeframe on this?

I'm having this issue several times a day! Brings my quad-core i5 3,1Ghz to over 50% of CPU usage.. constantly. I have to notice it first, then force-quit, which crashes Echofon every time. Extremely annoying and makes me want to stop using Growl once and for all. Unfortunately.. :/

[Chris Forsythe]

Growl 2 has only crashes and this issue targeted to it now, any new features are already complete and were worked on while the root cause of this high cpu issue was being investigated. Resolving this issue requires rewriting the entire networking stack, which is not a small task. It wouldn't matter if it were done for Growl 1.4.1, 1.4.2, 1.5, 2, 2000, or some other random number. 

To be clear about what's left for Growl 2, here is what's left:

http://code.google.com/p/growl/issues/list?can=2&q=Product%3DGrowl+Milestone%3D2.0+&colspec=ID+Type+Status+Priority+Milestone+Owner+BlockedOn+Summary+Product&cells=tiles

That's it. We have a start at login issue, 2 crash issues, looking into the switch making a bit more sense to some people, and then making sure that things are set up for localization properly. That's it. There are no new features. This issue has had our attention ever since it was first reported, we've spent more time on this than on any other single feature/issue/bug in the last 10 years. I'm sorry that you feel it's not being resolved quickly enough, but if we don't do this right we could end up putting out a version with another issue, and then another, etc etc.

This issue is unfortunately just taking time, and that's the bottom line. I hope this explanation covers a bit more ground so that you understand where we're at with this.

-- 
Chris Forsythe

@The_Tick

On Friday, July 20, 2012 at 10:17 AM, Kevin Yank wrote:

I agree with Carsten. Development on 2.0 should stop immediately to make time for a 1.4.1 to fix this critical issue. Consider that most new Mac users today use MacBooks, and right now Growl turns into a battery-guzzling monster several times a day without notice.

As a longtime Growl user, given this level of service for what is now a paid product, I find myself hoping for all my apps to ditch Growl and switch to 10.8’s Notification Center right away. :(

--

Kevin Yank

http://kevinyank.com/

--

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/-/jb79unvn76QJ.

[Kevin Yank]

Thanks for the additional background, Chris.

While this issue awaits a solution, it would be nice if the FAQ on the website covered this issue.

--

Kevin Yank

http://kevinyank.com/

[Chris Forsythe]

Not at lot of people have been looking at the FAQ actually, per web stats.

-- 
Chris Forsythe

@The_Tick

Attachments:

- smime.p7s

[Christopher Forsythe]

We're continuing to test the beta of Growl 2, and so far nobody has run into the CPU issue. There are other issues to work through, but I am confident that we've bagged this one in Growl 2.

Chris

On Thu, Aug 16, 2012 at 6:51 AM, Fabio Porto <fabi...@gmail.com> wrote:

Same problem here... sometimes it's go to 120% usage.

There is more problems on it, because my battery lose energy so fast... and my core2duo go to 84ºC!

Waiting for solution. :/

Sorry for my english guys, but I am brazilian. 

Thanks!

Em sexta-feira, 25 de novembro de 2011 09h38min01s UTC-2, dereinevogelda escreveu:

I'm using Growl 1.3.1 on OS X 10.7.2 and Safari 5.1.1.
After a while Growl increases CPU-usage for now up to 150% on a 2011
MacBook Pro 13" with Core i5 Dual Core CPU. If i stop Growl via kill
or Activity monitor and restart it, it works fine for several days
again.

As i read this group partial this is happening several times to other
Growl-users.

Regards
Mark

--
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/-/Y0ZAsTHcfuwJ.

To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.

--
Chris Forsythe

@The_Tick