I've been discussing it back and forth on growl-development, but identifying the source of the problem seems to have stalled.
We're probably seeing it more often with large batches of updates (such as the ones sometimes sent by Twitterrific) because, if you think about it in terms of probability and assuming notifications are independent events (probably a bad assumption), its more likely that the crash will occur when you have a batch of 10 notifications versus a single notification. I'll probably do some regression testing if I get the time and hopefully find a build where the crash doesn't occur. That should get us closer to identifying the problem. There certainly should be no problems with Growl handling a large batch of notifications at once, and while I highly doubt that's the problem if it is the problem then that needs to be fixed anyway. Bryan On Mar 10, 2009, at 1:26 PM, cortig wrote: > > Hi Brian, > > I reported a similar issue on Dec 11 2008 (look for a thread called > “GrowlHelperApp crashes”. > In my case, OmniGrowl was the application making GrowlHelperApp crash. > It looks to me like GrowlHelperApp has an issue when it gets too many > updates sent in a short period of time by an application. I suspect > that this is also the issue you are having with Twitterrific. > > The workaround for me was, sadly, to disable some of the > notifications. Now OmniGrowl is fine and doesn' induce any > GrowlHelperApp crash (but I only use a fraction of what I could use it > for). > > No word on whether a bug in GrowlHelperApp has been identified and > would be corrected though, > > Corentin > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
