How do you have your soundactions configured? On Tue, Jan 29, 2013 at 8:38 AM, <[email protected]> wrote:
> On login, I have a number of applications start automatically that I use > throughout the day. One of those is Mail, with GrowlMail. Most mornings I > have a number of emails waiting, which causes Growl to (try to) pop up > notifications. Starting earlier this January, after some update (of Mail > and GrowlMail, I think), Growl will show two or three notifications, beep > once, stop, then crash. The crash is in the same place consistently, in > what appears to be a routine associated with the soundaction. If I then > start Growl running again, it's fine until I log out again. > > Is this a known bug? Any workarounds? > > OS X 10.7.5, Mail 5.3, Growl 2.0.1, GrowlMail 1.3.5 > > I've been trying to attach the crash report but keep getting an error. > I'll include here what I hope are the relevant parts: > > Process: Growl [6726] > Path: /Applications/Growl.app/Contents/MacOS/Growl > Identifier: com.Growl.GrowlHelperApp > Version: 2.0.1 (2.0.1) > App Item ID: 467939042 > App External ID: 12183453 > Code Type: X86-64 (Native) > Parent Process: launchd [6604] > > Date/Time: 2013-01-28 08:53:53.659 -0500 > OS Version: Mac OS X 10.7.5 (11G63b) > Report Version: 9 > > Crashed Thread: 5 Dispatch queue: > com.growl.soundaction.sounddispatchqueue > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020 > > VM Regions Near 0x20: > --> > __TEXT 0000000103478000-000000010351b000 [ 652K] > r-x/rwx SM=COW /Applications/Growl.app/Contents/MacOS/Growl > > Application Specific Information: > objc[6726]: garbage collection is OFF > > [snip] > > Thread 5 Crashed:: Dispatch queue: com.growl.soundaction.sounddispatchqueue > 0 com.apple.AppKit 0x00007fff85d87c35 -[NSSound > _updateVolumeByStoredVolume] + 30 > 1 com.apple.AppKit 0x00007fff85d87e21 -[NSSound play] + > 83 > 2 com.growl.soundaction 0x000000010640581f > __43-[GrowlSoundAction sound:didFinishPlaying:]_block_invoke_0 + 212 > 3 libdispatch.dylib 0x00007fff84a6ea82 > _dispatch_call_block_and_release + 18 > 4 libdispatch.dylib 0x00007fff84a702d2 > _dispatch_queue_drain + 264 > 5 libdispatch.dylib 0x00007fff84a7012e > _dispatch_queue_invoke + 54 > 6 libdispatch.dylib 0x00007fff84a6f928 > _dispatch_worker_thread2 + 198 > 7 libsystem_c.dylib 0x00007fff88b6b3da _pthread_wqthread > + 316 > 8 libsystem_c.dylib 0x00007fff88b6cb85 start_wqthread + > 13 > > [snip] > > Thread 5 crashed with X86 Thread State (64-bit): > rax: 0x0000000000000000 rbx: 0x00007fa633ba33e0 rcx: > 0x0000000000000020 rdx: 0x0000000000000000 > rdi: 0x00007fa633ba33e0 rsi: 0x00007fff8613b647 rbp: > 0x0000000103881df0 rsp: 0x0000000103881de0 > r8: 0x0000000000000000 r9: 0x0000000000000300 r10: > 0x0000000000000081 r11: 0x00007fff85d87c17 > r12: 0x00007fa633ba9d40 r13: 0x0000000000000000 r14: > 0x00007fa633ba33e0 r15: 0x00007fff9179fe80 > rip: 0x00007fff85d87c35 rfl: 0x0000000000010202 cr2: 0x0000000000000020 > Logical CPU: 1 > > > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/growldiscuss?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Chris Forsythe @The_Tick <http://twitter.com/The_Tick> -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/growldiscuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
