Unfortunately this is something that we just didn't know about until after 1.3 came out. Basically it's a known issue. We tried fixing it for 1.4, but needed to submit Growl 1.4 to get other fixes out, so we're working on the solution here.
As soon as we have a fix and test it, we'll get it out. Luckily we have a lot more people who are testing for us now, so we're able to more easily hit more problems. Some of them run into this issue as well, so that's what our plan is to have them test it along with us. I do not have an ETA other than to say that our Lead Developer is working on this and only this problem until it is resolved. Chris On Thu, May 24, 2012 at 1:14 PM, Joe K. <[email protected]> wrote: > I've seen this just a couple of times, and I'm not sure what really causes > it. I hear my fans start spinning up because the processor is working hard > and heating up. When I check Activity Monitor, Growl is using over 100% > (two processors). When I click on the Growl icon in the Menubar, growl > crashes and it appears to send a crash report. > > -- > Joe > > -- > 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/-/GtsWnh4GYvwJ. > 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.
