brettpoole / growl

Automatically exported from code.google.com/p/growl
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

pthread crash in Growl 1.3.2 #408

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
See attached crash log.

Original issue reported on code.google.com by ch...@growl.info on 22 Dec 2011 at 6:58

Attachments:

GoogleCodeExporter commented 8 years ago
Similar issue happening daily here - will upload crash log on next occurrence.

Original comment by mannionp on 24 Dec 2011 at 1:12

GoogleCodeExporter commented 8 years ago
I'm facing the same issue. Every day growl crashes a few times, which slowly 
drives me crazy...

Original comment by amachni...@gmail.com on 27 Jan 2012 at 7:46

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by ch...@growl.info on 7 Feb 2012 at 11:42

GoogleCodeExporter commented 8 years ago
I've been churning on this for a bit now and i'm not any closer to figuring out 
how to trigger it.  is there anything you can think of in your daily ritual 
that could contribute? its very clear from the backtrace that you're clicking 
on the icon in the menubar, did a batch of notifications come in? were they 
fading out?

Original comment by r...@growl.info on 9 Feb 2012 at 2:32

GoogleCodeExporter commented 8 years ago
In my case, the machine is idle and the screensaver active/screen dimmed. It is 
not hibernating, and all my other processes are running without any issues 
reported.

Original comment by mannionp on 9 Feb 2012 at 2:49

GoogleCodeExporter commented 8 years ago
you didn't happen to run any system modification apps that touch HIToolbox.rsrc 
or the like, did you?

Original comment by rarich...@gmail.com on 9 Feb 2012 at 8:01

GoogleCodeExporter commented 8 years ago
possibly one of the tweaks from this? http://ifredrik.com/applications/

Original comment by r...@growl.info on 10 Feb 2012 at 3:06

GoogleCodeExporter commented 8 years ago
The reason for this crash is a corrupt HIToolbox.rsrc. There's not anything we 
can do on this, since it's Apple's code.

Please file a ticket at http://bugreporter.apple.com about this issue. Maybe 
Apple can do something good here, but it's not within our control.

Original comment by ch...@growl.info on 18 Feb 2012 at 1:16