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/** >>> msg/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@* >>> *googlegroups.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. > > 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.
