On Sep 23, 2008, at 06:34:36, Phil wrote: > As a follow up to this problem, I have had 0 crashes in the last 3-4 > days since disabling Growl, so I am not pretty convinced that it was > the cause.
What display style are you using? Can you reproduce the problem (i.e., lock up your system) if you directly force a notification to happen? If so, can you use Shark to take a system trace, starting immediately before you make the notification happen? (System Trace runs for five seconds or less, so you'd have that much time to make a notification happen after you hit Option-Escape.) > Does no one know what causes the "GrowlHelperApp[174] <Error>: > doClip: empty path" error messages in the system log? It's probably drawing-related. It sounds like it's trying to set the clipping path to an empty path (no subpaths), which is definitely an error. That said, setting the clipping path to an empty path isn't the sort of bug that would lock up a modern, memory-protected, preemptively- scheduled system. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
