The workaround we have for this for right now is to quit Growl and then restart it. The problem builds up over time. We're working on addressing the issue.
Chris On Tue, Jun 26, 2012 at 3:21 PM, bocaboy <[email protected]> wrote: > Count me in as one of the people having high CPU usage with Growl 1.4. I > am using a pre-release of 10.7.5, but the problem also occurred in 10.7.4. > Ironically, the error occurs frequently on my MacBook Pro, but never occurs > on my iMac. > > On Friday, June 22, 2012 11:50:35 AM UTC-4, alanfluff wrote: >> >> 10.7.4 OS X and 1.4 Growl and Growl will about three times per 8 hour day >> just eat the processor and everything begins to crawl and clicking the >> Growl icon in the menu bar causes Growl to quit. >> >> This has been happening _since_ 1.4 (was not happening pre 1.4). >> >> If I understand it right and 1.4 had to ship even tho this was known >> about then it would have been good if the u/g to 1.4 cam with a health >> warning explaining this. If that was not possible and it was impossible not >> to ship then something somewhere with this delivery process within Apple or >> the Growl team is patently well and truly broken and it's a sad sad >> situation to quote Elton :( >> >> Good luck Growl team with your 1.4.X fix and here's hoping it comes out >> soon. >> >> >> On Tuesday, 19 June 2012 01:40:10 UTC-4, Christopher Forsythe wrote: >>> >>> If we didn't care we wouldn't be fixing it nor would we be replying here. >>> >>> On Mon, Jun 18, 2012 at 12:07 PM, Dmitriy <[email protected]> wrote: >>> >>>> I think they just don't care... >>>> >>>> >>>> On Sunday, June 17, 2012 7:10:34 AM UTC+4, John Dyer wrote: >>>>> >>>>> Team, >>>>> >>>>> So what is the workaround in the meantime for this? I mean the app >>>>> is totally unusable as it stands, and the fact that you shipped a new >>>>> version without fixing this longstanding bug is really quite crappy. >>>>> >>>>> -John >>>>> >>>>> On Wednesday, 13 June 2012 18:29:46 UTC-4, Christopher Forsythe wrote: >>>>>> >>>>>> As Daniel mentioned in another thread, this issue is something we're >>>>>> working on fixing, but that we just couldn't get into Growl 1.4 in time. >>>>>> 1.4 has a ton of fixes and improvements that needed to go out before the >>>>>> sandboxing deadline, so that's why we shipped it without fixing this >>>>>> issue. >>>>>> It's still high on our list, but it takes rewriting the networking to fix >>>>>> it which is taking some time. >>>>>> >>>>>> -- >>>>>> Chris Forsythe >>>>>> @The_Tick <http://twitter.com/The_Tick> >>>>>> >>>>>> On Wednesday, June 13, 2012 at 2:29 PM, freshh29 wrote: >>>>>> >>>>>> Here the same... look my Post >>>>>> >>>>>> Am Mittwoch, 13. Juni 2012 16:05:39 UTC+2 schrieb Guy >>>>>> Gascoigne-Piggford: >>>>>> >>>>>> I leave my macbook pro on every night, this morning I get to it to >>>>>> find that the fan is running full speed (apparently it was doing it in >>>>>> the >>>>>> middle of the night as well, my wife noticed). Activity monitor shows >>>>>> the >>>>>> usual mass or apps running, with Growl pegging one of the cpus (at 108%) >>>>>> and everything else pretty much doing noting. This is on 10.7.4. CPU >>>>>> usage dropped back to expected after I killed Growl and restarted it. >>>>>> >>>>>> Now I realize that this isn't much of a bug report, but are there any >>>>>> logs or other trace information that I could enable or upload that might >>>>>> help diagnose what's going on? >>>>>> >>>>>> Thanks - Guy >>>>>> >>>>>> -- >>>>>> 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/ >>>>>> **ms**g/growldiscuss/-/**svcFYP6c0r8J<https://groups.google.com/d/msg/growldiscuss/-/svcFYP6c0r8J> >>>>>> . >>>>>> To post to this group, send email to [email protected]. >>>>>> To unsubscribe from this group, send email to >>>>>> growldiscuss+unsubscribe@**googl**egroups.com<[email protected]> >>>>>> . >>>>>> For more options, visit this group at http://groups.google.com/** >>>>>> group**/growldiscuss?hl=en<http://groups.google.com/group/growldiscuss?hl=en> >>>>>> . >>>>>> >>>>>> >>>>>> -- >>>> 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/-/**9h4N66l0wOcJ<https://groups.google.com/d/msg/growldiscuss/-/9h4N66l0wOcJ> >>>> . >>>> >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to growldiscuss+unsubscribe@ >>>> **googlegroups.com <growldiscuss%[email protected]>. >>>> For more options, visit this group at http://groups.google.com/** >>>> group/growldiscuss?hl=en<http://groups.google.com/group/growldiscuss?hl=en> >>>> . >>>> >>> >>> >>> >>> -- >>> Chris Forsythe >>> @The_Tick <http://twitter.com/The_Tick> >>> >>> -- > 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/-/ZYDy09s5SDAJ. > > 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. > -- Chris Forsythe @The_Tick <http://twitter.com/The_Tick> -- 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.
