Sorry, Zac - I think I understand the issue, but I still don't understand why I'm only hitting this problem with Growl 1.3.2. Growl 1.3 and 1.3.1 worked fine for me.
On Dec 11, 3:55 pm, Zac Bowling <[email protected]> wrote: > Chris, > > That is a different issue. > > Your hitting a bug I've ran into before in WebKit in the past. A few of my > customers were hitting this same issue when Lion was released and I haven't > narrowed exactly what is in their configuration that causes it to happen for > them. I filed a radar with Apple and still waiting in a response. > > In the mean time I put in a work around into Growl that I'm going to try and > work in for the next release. What happens is that when we are destroying the > Growl notification, we try to clean up safely and null out a callback that > webkit uses to talk back to us on. The issue is that webkit uses a weird > forwarding pattern that doesn't always respond consistently from that I can > tell. The work around ignores when we can't but because since we don't get to > null it out, there is still a potential that another kind of issue can happen > later if it tries to callback and talk to us before it's fully destroyed. > Unfortunately all we can do is work around it until Apple can investigate and > fix the bug. > > Zac > > -- > Zac Bowling -- 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.
