On Jan 29, 4:28 pm, Peter Hosey <[email protected]> wrote:
> On Jan 29, 2010, at 12:10:12, Michael Newman wrote:
>
> > Every once in a while since switching to Snow Leopard I have found  
> > Growl Helper App just goes off into its own little world,  
> > effectively stalling all connections to it and eating up near 100%  
> > of my CPU.
>
> Please take a sample using the Activity Monitor and send us the sample.


Sampling process 310 for 3 seconds with 1 millisecond of run time
between samples
Sampling completed, processing symbols...
Analysis of sampling GrowlHelperApp (pid 310) every 1 millisecond
Call graph:
    2349 Thread_1007   DispatchQueue_1: com.apple.main-thread
(serial)
      2349 start
        2349 main
          2349 -[GrowlApplication run]
            2349 -[NSApplication run]
              2349 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:]
                2349 _DPSNextEvent
                  2349 BlockUntilNextEventMatchingListInMode
                    2349 ReceiveNextEventCommon
                      2349 RunCurrentEventLoopInMode
                        2349 CFRunLoopRunSpecific
                          2349 __CFRunLoopRun
                            2349 __CFRunLoopDoSources0
                              2349 MultiplexerSource::perform()
                                2349
URLConnectionClient::processEvents()
                                  2349
URLConnectionClient::ClientConnectionEventQueue::processAllEventsAndConsumePayload(XConnectionEventInfo<XClientEvent,
XClientEventParams>*, long)
                                    2349
URLConnectionClient::ClientConnectionEventQueue::processAllEventsAndConsumePayload(XConnectionEventInfo<XClientEvent,
XClientEventParams>*, long)
                                      2349
URLConnectionClient::_clientDidFinishLoading(URLConnectionClient::ClientConnectionEventQueue*)
                                        2349
_NSURLConnectionDidFinishLoading
                                          2349
WebCore::SubresourceLoader::didFinishLoading()
                                            2349
WebCore::DocumentLoader::removeSubresourceLoader(WebCore::ResourceLoader*)
                                              2349
WebCore::FrameLoader::recursiveCheckLoadComplete()
                                                2349
WebCore::FrameLoader::checkLoadCompleteForThisFrame()
                                                  2349
WebFrameLoaderClient::dispatchDidFinishLoad()
                                                    2349
CallFrameLoadDelegate(objc_object* (*)(objc_object*,
objc_selector*, ...), WebView*, objc_selector*, objc_object*)
                                                      2349 -
[GrowlWebKitWindowController webView:didFinishLoadForFrame:]
                                                        2295 -
[GrowlPositionController positionDisplay:]
                                                          1841
NSIntersectsRect
                                                          378 -
[GrowlPositionController positionDisplay:]
                                                          76
NSContainsRect
                                                        42
dyld_stub_NSIntersectsRect
                                                        12
dyld_stub_NSContainsRect
    2349 Thread_1034   DispatchQueue_2: com.apple.libdispatch-manager
(serial)
      2349 start_wqthread
        2349 _pthread_wqthread
          2349 _dispatch_worker_thread2
            2349 _dispatch_queue_invoke
              2349 _dispatch_mgr_invoke
                2349 kevent
    2349 Thread_1277
      2349 thread_start
        2349 _pthread_start
          2349 __NSThread__main__
            2349 -[NSConnection run]
              2349 CFRunLoopRunSpecific
                2349 __CFRunLoopRun
                  2349 mach_msg
                    2349 mach_msg_trap
    2349 Thread_1436: JavaScriptCore: FastMalloc scavenger
      2349 thread_start
        2349 _pthread_start
          2349 WTF::TCMalloc_PageHeap::runScavengerThread(void*)
            2349 WTF::TCMalloc_PageHeap::scavengerThread()
              2349 sleep
                2349 nanosleep
                  2349 __semwait_signal
    2349 Thread_1439
      2349 thread_start
        2349 _pthread_start
          2349 __NSThread__main__
            2349 +[NSURLConnection(NSURLConnectionReallyInternal)
_resourceLoadLoop:]
              2349 CFRunLoopRunSpecific
                2349 __CFRunLoopRun
                  2349 mach_msg
                    2349 mach_msg_trap
    2349 Thread_1471144
      2349 thread_start
        2349 _pthread_start
          2349 __CFSocketManager
            2349 select$DARWIN_EXTSN
    2349 Thread_1801144
      2349 start_wqthread
        2349 _pthread_wqthread
          2349 __workq_kernreturn
    1 Thread_1800276
      1 start_wqthread
        1 _pthread_wqthread
          1 __workq_kernreturn

Total number in stack (recursive counted multiple, when >=5):

Sort by top of stack, same collapsed (when >= 5):
        mach_msg_trap        4698
        __workq_kernreturn        2350
        __semwait_signal        2349
        kevent        2349
        select$DARWIN_EXTSN        2349
        NSIntersectsRect        1841
        -[GrowlPositionController positionDisplay:]        378
        NSContainsRect        76
        dyld_stub_NSIntersectsRect        42
        dyld_stub_NSContainsRect        12
Sample analysis of process 310 written to file /dev/stdout


Thanks for looking at this. This only occurs when going from multiple
monitors to one and there is something with it going to sleep sometime
during the process.

I wish I could be more helpful.

Christopher, I apologize I waited so long, and you asked why it did so
here is my list:
1.) it's not that serious of an issue, this computer has 4 cores and
one only effects my programs that are looking for a Growl Connection.
2.) I was looking for a Trac or GitHub or some other site where I
could actively download the source so I could look into actually
giving a patch with my description, and eventually decided that it was
better to report then look into fixing.
3.) I was looking for a formal bug tracking system. I am not used to
filing bugs on Google Groups and so it took me a while.
4.) Because the attitude of this list is such that I knew if I were to
post, I would get a flippant response like that.

I say this all in jest and know we are all doing this out of the
goodness of our hearts, but this is my first problem with Growl and
forgive me for having other priorities.

Michael

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