This is still happening with me on 1.3.2 . I've already posted a sample.
This happens consistently whenever Growl is left running for a few hours—100% reproducible, though there are NO specific steps other than "launch growl, leave computer running" One additional bit of info: when I look at the process list in iStats Menu "launchd" is the process taking all the CPU. Activity monitor still shows the "Growl" as the process taking all the CPU. This has become completely unusable—I've uninstalled Growl 1.3.2 and reverted to 1.2.2 :-( -- 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.
