Not at lot of people have been looking at the FAQ actually, per web stats.
-- Chris Forsythe @The_Tick (http://twitter.com/The_Tick) On Friday, July 20, 2012 at 10:55 PM, Kevin Yank wrote: > 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/ > > > On 21/07/2012, at 1:08 PM, Chris Forsythe <[email protected] > (mailto:[email protected])> wrote: > > 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 (http://twitter.com/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 (http://kevinyank.com/)/ > > > > > > > > > On Thursday, July 12, 2012 5:38:42 AM UTC+10, Daniel Siemer wrote: > > > > 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 view this discussion on the web visit > > > https://groups.google.com/d/msg/growldiscuss/-/jb79unvn76QJ. > > > To post to this group, send email to [email protected] > > > (mailto:[email protected]). > > > To unsubscribe from this group, send email to > > > [email protected] > > > (mailto:[email protected]). > > > 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 [email protected] > > (mailto:[email protected]). > > To unsubscribe from this group, send email to > > [email protected] > > (mailto:[email protected]). > > For more options, visit this group at > > http://groups.google.com/group/growldiscuss?hl=en. > > > Attachments: > - smime.p7s > -- 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.
