We know the source of this bug, however, getting it fixed was going to take much longer than we had for 1.4 due to the sandboxing deadline, and 1.4 has a number of fixes and improvements that needed to ship. The best stop gap for now is to quit or force quit growl and relaunch it when it starts doing it. We got into this situation by not being careful enough with the design and implementation of the previous networking stack, so we are going to take the time we need to make sure its right this time. Growl 2.0 is the intended target for the new networking stack.
On Jun 13, 12:48 pm, freshh29 <[email protected]> wrote: > Sorry yes .... i have 5 Report in console for Growl > > Am Mittwoch, 13. Juni 2012 02:15:42 UTC+2 schrieb freshh29: > > > > > > > > > > > Newest Lion > > Newest Growl MAS > > > After newest Update from time to time my MAC runs hot while Mac need > > 100 % of CPU... this is the 3 rd day > > > It don't stop from alone. I must end Growl...and restart then works > > fine for few hours > > > Please fix -- 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.
