If it comes back, get a sample immediately and anything else you can think of that might help.
On Tue, Jan 15, 2013 at 5:30 AM, Konrad Rudolph <[email protected]>wrote: > For what it’s worth I’ve been observing the CPU consumption for several > months since the upgrade now and I haven’t been able to reproduce a case > where Growl went haywire so I’m assuming that the initial issue must have > been caused by something else. > > Cheers, > Konrad > > -- > 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/-/uCX9zpt8LGIJ. > > 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.
