Hi - I was the original reporter of this issue. I can reproduce this both with Path Finder and Linkinus. It doesn't matter if it's at launch, but the first launch of any app that uses Growl notification either hang, or takes a really long time to launch (3-5 minutes). Killing the GrowlHelperApp process causes the hanging app to immediately launch.
I sampled the GrowlHelperApp during one of these hangs - http://neil.io/su3F I've tried completely uninstalling growl and deleting all traces of its support files from my system and reinstalling a fresh copy, but the issue eventually returns. Any ideas? On Feb 16, 9:22 pm, sgehrman <[email protected]> wrote: > It seems to be a rare problem and it only happens if Path Finder is > set to launch at login. I told him to sample GrowlHelperApp as well. > I'll let you know if I get any more info. > > -steve > > On Feb 15, 11:58 pm, Peter Hosey <[email protected]> wrote: > > > On Feb 15, 2010, at 23:37:40, Steve Gehrman wrote: > > > > I'm still getting reports of thishang. > > > I've been running PF 5.5.8 for 24 days and have not seen it once. > > > > 8424 +[GrowlApplicationBridge > > > setGrowlDelegate:] > > > 8424 +[GrowlApplicationBridge > > > _launchGrowlIfInstalledWithRegistrationDictionary:] > > > 8424 AESendMessage > > > 8424 sendToModernProcess > > > (__CFMachPort*, unsigned long, AEDesc const*, long) > > > Can you get them to sample GrowlHelperApp as well? -- 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.
