Re: Growl 1.4 pegs cpu for hours

[freshh29]

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

[Chris Forsythe]

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

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

[John Dyer]

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

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

[Dmitriy]

I think they just don't care...

[Peter N Lewis]

On 19/06/2012, at 1:07 , Dmitriy wrote:
> I think they just don't care…

That doesn't seem entirely fair.

My guess is that they have been forced to fit in with Apple's sandboxing, which has forced them to change the way their SDK and Growl communicate, which has forced them into network coding. And network coding is hard - there is a reason so many cloud and data sharing systems have come and gone, with endless stories of data corruption. Networking code and Threading are two of the hardest programming problems, and they inevitably go hand in hand as you can't expect a network connection to respond immediately, even a local network connection.

I agree, Growl is at its worst state it has been in for years, and the timing sucks, but for some of that you can blame Apple for forcing sandboxing and other restrictions on the Mac App Store, which took the time frame out of developers hands.

Certainly I hope things in Growl land improve soon - I'm terrified to ship the next bugfix version of Keyboard Maestro with the new Growl SDK - but to say to developers who have worked on a free product for years before asking for a measly couple bucks that "they just don't care" is not fair.

IMHO anyway.
Peter.

--
Keyboard Maestro 5.3 now available - new image actions, enhanced Mouse Click action and more.

Keyboard Maestro <http://www.keyboardmaestro.com/> Macros for your Mac
<http://www.stairways.com/> <http://download.stairways.com/>

[Christopher Forsythe]

If we didn't care we wouldn't be fixing it nor would we be replying here.

To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/9h4N66l0wOcJ.

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

[Christopher Forsythe]

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 <boc...@gmail.com> 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.

Chris Forsythe

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