Ya, I see your @growlmac tweets when you send them. I definitely know
you're having this problem. Until we have something to test though, I don't
have a better solution other than to load 1.2.2 until we have the problem
fixed. I'm sorry, you folks are just running into something that

a) nobody ran into while testing 1.3

and b) we're having to rewrite large amounts of code to address.

Chris

On Wed, Jun 13, 2012 at 1:14 PM, Shelby DeNike <[email protected]> wrote:

> Hi Chris,
>
> I am having this issue and have to close Growl multiple times through the
> day, if there is anything I can do to test that would be great since this
> is very common on my system.
>
> Thanks,
>
> Shelby
>
> On Monday, June 4, 2012 6:31:16 PM UTC-7, Christopher Forsythe wrote:
>>
>> 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<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 growldiscuss+unsubscribe@*
>>> *googlegroups.com <growldiscuss%[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>
>>> .
>>>
>>
>>
>>
>> --
>> 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 view this discussion on the web visit
> https://groups.google.com/d/msg/growldiscuss/-/puKrZtOAqboJ.
>
> 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.

Reply via email to