On Aug 4, 1:24 am, Peter Hosey <[email protected]> wrote:
> On Aug 3, 2010, at 22:17:33, Ryan Petty wrote:
>
> > anything I can do to help? more logs, answer questions??
>
> What we need is a way to reliably reproduce the crash so that we can make it
> happen in the debugger, or at least add log statements, until we find the
> cause.
>
> I do notice that Bezel and Nano are both queueing displays, so that's step
> one. That said, I've been using Music Video, another queueing display, and it
> works just fine. I also have just tried Bezel and Nano and couldn't get them
> to crash. So, we need more steps that lead to a crash.
>
> If you turn on logging, Growl will log every notification it receives (among
> other things, as some users started another thread about). You can use this
> to find out what the last notification Growl received before it crashed was.
I have logging turned on. Growl just crashed and the last
notification was from SpamSieve. Then, there was this message in the
log (I'm not sure if it is normal or not):
Aug 9, 2010 3:03:06 PM Reserving rect NSRect: {{0, -96}, {1680,
96}}
--
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.
