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 <[email protected]> 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 > > Den onsdag den 27. juni 2012 06.19.21 UTC+2 skrev 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 -- 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.
