That crash is kind of an odd backtrace, and while I know where it occurs roughly, I don't know why. It certainly wouldn't have existed in Growl 1.2.2 (there has been no Growl 1.2.3, did you mean 1.3.2?). This is the result of the history database trim functions, but the full backtrace shows its having problems unpacking a dictionary from within the history database. If it went in, not sure why it wouldn't come back out. Im not entirely sure on a workaround, but as one option, you could try turning off history for the time being (in the history tab of Growl's preferences). Growl 2.1 should lessen the likely hood of this failure as any notifications coming from apps using frameworks 1.3 or newer, but it isn't a true fix (especially as I don't know for certain that this is the click context that is failing to be unarchived).
I have filed this as http://code.google.com/p/growl/issues/detail?id=569, which you can follow our progress on. If you have any further info that might help, please add it there, like a list of apps you get notifications from, particularly any that might be less widely used. If it continues to persist, we might ask for a copy of the databases (history and tickets/display configs) to test against On Dec 6, 5:08 pm, Brian Coia <[email protected]> wrote: > Nope, nothing. Console remains empty. Growl's menubar icon will persist > through the crash until I roll over it, or enter sleep, or do anything else > that causes the menubar to refresh and realize Growl crashed. > > > > > > > > On Thursday, December 6, 2012 11:39:58 AM UTC-6, Chas4 wrote: > > > Notice anything Growl does before it crashes? Does the console say > > anything before the crash happens? > > > On Wed, Dec 5, 2012 at 10:07 PM, Brian Coia <[email protected]<javascript:> > > > wrote: > > >> I've had an issue with Growl since version 1.2.3 where Growl silently > >> crashes after being open for roughly 10 minutes. Version 1.2.2 is the only > >> version that doesn't do this. > > >> Growl 2.0 was no different. I just updated to Growl 2.0.1, hoping the > >> issue would finally be resolved. But unfortunately, it's still crashing. > > >> I've tried using the Growl uninstaller, as well as manually removing all > >> of Growl's files. Nothing seems to help. > > >> Here the most recent crash > >> log<http://pastie.org/private/i6ifd3yenos4q7uhfm0y8g>. > >> Anything I could try? Could it be a conflict with other software, or maybe > >> it's due to an old style, or..? Help! > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Growl Discuss" group. > >> To view this discussion on the web visit > >>https://groups.google.com/d/msg/growldiscuss/-/Z7kJnpiZM38J. > >> To post to this group, send email to > >> [email protected]<javascript:> > >> . > >> To unsubscribe from this group, send email to > >> [email protected] <javascript:>. > >> For more options, visit this group at > >>http://groups.google.com/group/growldiscuss?hl=en. > > > -- > > > ---- > > Charlie Schloss > > > Grab Opera the fastest browser on earth @ > >http://my.opera.com/community/download.pl?ref=Chas4&p=opera_desktop > > > Why Open the Web? > > > Despite the connecting purpose of the Web, it is not entirely open to all > > of > > its users. When used correctly, HTML documents can be displayed across > > platforms and devices. However, many devices are excluded access to Web > > content. > > >http://my.opera.com/community/openweb/info/ -- 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.
