Hey! thanks for the heads up as well.  and now that I'm up and running with 
growl I'm loving it. and thanks to the growl folks on twitter who have been 
helping me as well. Mine has not crashed yet I don't think but if it does I'll 
also sen d in consul logs if necessary.
On Jan 28, 2012, at 2:07 PM, smilinggoat wrote:

> Great to hear it Daniel.  Thanks for the update!
> 
> On Jan 26, 10:38 am, Daniel Siemer <[email protected]> wrote:
>> Huzzah, we at last have a reproducible case on the CFGetErrorDomain
>> crash, and where it is happening in our code. Growl under heavy load
>> (and possibly less heavy loads) of incoming notes, with say, Mono (I
>> even got it to happen with 2.0), and possibly other webkit styles,
>> would hang.  We are investigating this, and will have a fix in at
>> least the next version we send in to Apple.  (We submitted 1.3.3 as of
>> yesterday, so likely this will get pushed to 1.4, which is getting
>> ready for beta).
>> 
>> On Jan 26, 1:40 am, Neil Turner <[email protected]> wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> The app actually crashes. However, I've found that updating to version
>>> 2.0 of the Mono display style fixed the problem.
>> 
>>> On Jan 25, 1:05 pm, AlbertTCB <[email protected]> wrote:
>> 
>>>> Since Growl 1.3.2 also crashes randomly on mine iMac, I'm curious
>>>> about your situation. Does the app actual crash, or do you notice that
>>>> you're not getting any notifications anymore and find the process not
>>>> to be responding anymore (in the activity window)? With me it doesn't
>>>> really crashes: the icon is still showing in the menubar but can't be
>>>> accessed or just. Killing the process and restart Growl is the only
>>>> solution (for the upcoming unknown amount of minutes/hours?)
>> 
>>>> On Jan 23, 8:24 am, Neil Turner <[email protected]> wrote:
>> 
>>>>> I too am having problems - crash log below. This is after clearing all
>>>>> Growl preferences with only 1Password, Boxcar, HardwareGrowler,
>>>>> Lighthouse, ScrobblePod and Twitter registered as applications. It
>>>>> happens on first boot, when Growl runs automatically along with
>>>>> Twitter, 1Password, HardwareGrowler, Lighthouse and ScrobblePod. Mono
>>>>> is the theme that I'm using.
>> 
>>>>> I have a hunch that Twitter is part of the problem as it fires off 3
>>>>> notifications in quick succession when it starts, and it looks like
>>>>> Growl tries to display the notifications but fails, as some thin black
>>>>> lines appear where the notifications should be.
>> 
>>>>> --
>> 
>>>>> Process:         Growl [333]
>>>>> Path:            /Applications/Growl.app/Contents/MacOS/Growl
>>>>> Identifier:      com.Growl.GrowlHelperApp
>>>>> Version:         1.3.2 (1.3.2)
>>>>> App Item ID:     467939042
>>>>> App External ID: 5158163
>>>>> Code Type:       X86-64 (Native)
>>>>> Parent Process:  launchd [235]
>> 
>>>>> Date/Time:       2012-01-23 07:13:15.091 +0000
>>>>> OS Version:      Mac OS X 10.7.2 (11C74)
>>>>> Report Version:  9
>> 
>>>>> Crashed Thread:  0  Dispatch queue: com.apple.main-thread
>> 
>>>>> Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
>>>>> Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
>> 
>>>>> VM Regions Near 0:
>>>>> -->
>>>>>     __TEXT                 000000010a7dc000-000000010a84f000 [  460K]
>>>>> r-x/rwx SM=COW  /Applications/Growl.app/Contents/MacOS/Growl
>> 
>>>>> Application Specific Information:
>>>>> objc[333]: garbage collection is OFF
>> 
>>>>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
>>>>> 0   com.apple.CoreFoundation            0x00007fff98d29482 
>>>>> CFErrorGetDomain
>>>>> + 18
>>>>> 1   com.apple.CFNetwork                 0x00007fff91dcf8f1
>>>>> URLConnectionClient::_clientDidFailWithError(__CFError*,
>>>>> URLConnectionClient::ClientConnectionEventQueue*) + 31
>>>>> 2   com.apple.CFNetwork                 0x00007fff91dced25
>>>>> URLConnectionClient::ClientConnectionEventQueue::processAllEventsAndConsume
>>>>>  Payload(XConnectionEventInfo<XClientEvent,
>>>>> XClientEventParams>*, long) + 885
>>>>> 3   com.apple.CFNetwork                 0x00007fff91cf9dfd
>>>>> URLConnectionClient::processEvents() + 185
>>>>> 4   com.apple.CFNetwork                 0x00007fff91cf9ca2
>>>>> MultiplexerSource::perform() + 212
>>>>> 5   com.apple.CoreFoundation            0x00007fff98c60b51
>>>>> __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
>>>>> 6   com.apple.CoreFoundation            0x00007fff98c603bd
>>>>> __CFRunLoopDoSources0 + 253
>>>>> 7   com.apple.CoreFoundation            0x00007fff98c871a9 __CFRunLoopRun 
>>>>> +
>>>>> 905
>>>>> 8   com.apple.CoreFoundation            0x00007fff98c86ae6
>>>>> CFRunLoopRunSpecific + 230
>>>>> 9   com.apple.HIToolbox                 0x00007fff998df3d3
>>>>> RunCurrentEventLoopInMode + 277
>>>>> 10  com.apple.HIToolbox                 0x00007fff998e663d
>>>>> ReceiveNextEventCommon + 355
>>>>> 11  com.apple.HIToolbox                 0x00007fff998e64ca
>>>>> BlockUntilNextEventMatchingListInMode + 62
>>>>> 12  com.apple.AppKit                    0x00007fff8fa9d3f1 _DPSNextEvent +
>>>>> 659
>>>>> 13  com.apple.AppKit                    0x00007fff8fa9ccf5 -[NSApplication
>>>>> nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
>>>>> 14  com.apple.AppKit                    0x00007fff8fa9962d -[NSApplication
>>>>> run] + 470
>>>>> 15  com.Growl.GrowlHelperApp            0x000000010a8007a9 -
>>>>> [GrowlApplication run] + 182
>>>>> 16  com.apple.AppKit                    0x00007fff8fd1880c
>>>>> NSApplicationMain + 867
>>>>> 17  com.Growl.GrowlHelperApp            0x000000010a7e88a5 main + 134
>>>>> 18  com.Growl.GrowlHelperApp            0x000000010a7ddbc4 start + 52
>> 
>>>>> Thread 1:: Dispatch queue: com.apple.libdispatch-manager
>>>>> 0   libsystem_kernel.dylib              0x00007fff958ec7e6 kevent + 10
>>>>> 1   libdispatch.dylib                   0x00007fff92fbe5be
>>>>> _dispatch_mgr_invoke + 923
>>>>> 2   libdispatch.dylib                   0x00007fff92fbd14e
>>>>> _dispatch_mgr_thread + 54
>> 
>>>>> Thread 2:
>>>>> 0   libsystem_kernel.dylib              0x00007fff958ea67a mach_msg_trap +
>>>>> 10
>>>>> 1   libsystem_kernel.dylib              0x00007fff958e9d71 mach_msg + 73
>>>>> 2   com.apple.CoreFoundation            0x00007fff98c7eb6c
>>>>> __CFRunLoopServiceMachPort + 188
>>>>> 3   com.apple.CoreFoundation            0x00007fff98c872d4 __CFRunLoopRun 
>>>>> +
>>>>> 1204
>>>>> 4   com.apple.CoreFoundation            0x00007fff98c86ae6
>>>>> CFRunLoopRunSpecific + 230
>>>>> 5   com.apple.Foundation                0x00007fff920d4fff -[NSConnection
>>>>> run] + 116
>>>>> 6   com.apple.Foundation                0x00007fff9207c7fe -[NSThread 
>>>>> main]
>>>>> + 68
>>>>> 7   com.apple.Foundation                0x00007fff9207c776
>>>>> __NSThread__main__ + 1575
>>>>> 8   libsystem_c.dylib                   0x00007fff97ac08bf _pthread_start 
>>>>> +
>>>>> 335
>>>>> 9   libsystem_c.dylib                   0x00007fff97ac3b75 thread_start +
>>>>> 13
>> 
>>>>> Thread 3:: com.apple.CFSocket.private
>>>>> 0   libsystem_kernel.dylib              0x00007fff958ebdf2 __select + 10
>>>>> 1   com.apple.CoreFoundation            0x00007fff98ccff9b
>>>>> __CFSocketManager + 1355
>>>>> 2   libsystem_c.dylib                   0x00007fff97ac08bf _pthread_start 
>>>>> +
>>>>> 335
>>>>> 3   libsystem_c.dylib                   0x00007fff97ac3b75 thread_start +
>>>>> 13
>> 
>>>>> Thread 4:
>>>>> 0   libsystem_kernel.dylib              0x00007fff958ec192
>>>>> __workq_kernreturn + 10
>>>>> 1   libsystem_c.dylib                   0x00007fff97ac2594
>>>>> _pthread_wqthread + 758
>>>>> 2   libsystem_c.dylib                   0x00007fff97ac3b85 start_wqthread 
>>>>> +
>>>>> 13
>> 
>>>>> Thread 5:: WebCore: LocalStorage
>>>>> 0   libsystem_kernel.dylib              0x00007fff958ebbca __psynch_cvwait
>>>>> + 10
>>>>> 1   libsystem_c.dylib                   0x00007fff97ac4274
>>>>> _pthread_cond_wait + 840
>>>>> 2   com.apple.JavaScriptCore            0x00007fff995665a0
>>>>> WTF::ThreadCondition::timedWait(WTF::Mutex&, double) + 64
>>>>> 3   com.apple.WebCore                   0x00007fff97bdad5a
>>>>> WTF::MessageQueue<WebCore::LocalStorageTask>::waitForMessage() + 132
>>>>> 4   com.apple.WebCore                   0x00007fff97bdacb3
>>>>> WebCore::LocalStorageThread::threadEntryPoint() + 99
>>>>> 5   com.apple.WebCore                   0x00007fff97bdabfb
>>>>> WebCore::LocalStorageThread::threadEntryPointCallback(void*) + 9
>>>>> 6   libsystem_c.dylib                   0x00007fff97ac08bf _pthread_start 
>>>>> +
>>>>> 335
>>>>> 7   libsystem_c.dylib                   0x00007fff97ac3b75 thread_start +
>>>>> 13
>> 
>>>>> Thread 6:
>>>>> 0   libsystem_kernel.dylib              0x00007fff958ec192
>>>>> __workq_kernreturn + 10
>>>>> 1   libsystem_c.dylib                   0x00007fff97ac2594
>>>>> _pthread_wqthread + 758
>>>>> 2   libsystem_c.dylib                   0x00007fff97ac3b85 start_wqthread 
>>>>> +
>>>>> 13
>> 
>>>>> Thread 7:: JavaScriptCore::BlockFree
>>>>> 0   libsystem_kernel.dylib              0x00007fff958ebbca __psynch_cvwait
>>>>> + 10
>>>>> 1   libsystem_c.dylib                   0x00007fff97ac4274
>>>>> _pthread_cond_wait + 840
>>>>> 2   com.apple.JavaScriptCore            0x00007fff995665f7
>>>>> WTF::ThreadCondition::timedWait(WTF::Mutex&, double) + 151
>>>>> 3   com.apple.JavaScriptCore            0x00007fff99792ccf
>>>>> JSC::Heap::blockFreeingThreadMain() + 319
>>>>> 4   com.apple.JavaScriptCore            0x00007fff99792d09
>>>>> JSC::Heap::blockFreeingThreadStartFunc(void*) + 9
>>>>> 5   libsystem_c.dylib                   0x00007fff97ac08bf _pthread_start 
>>>>> +
>>>>> 335
>>>>> 6   libsystem_c.dylib                   0x00007fff97ac3b75 thread_start +
>>>>> 13
>> 
>>>>> Thread 8:: com.apple.NSURLConnectionLoader
>>>>> 0   libsystem_kernel.dylib
>> 
>> ...
>> 
>> read more ยป
> 
> -- 
> 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.
> 

-- 
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.

Reply via email to