You're reporting a problem which has been fixed for the next release of Growl.
Cheers, Evan On Feb 15, 2010, at 11:54 PM, Piko wrote: > Same symptoms. Had to kill -15 the process and then do a restart to > get things back on track. Only started to hang like this after I > enabled GrowlSafari. Here's my sample: > > Analysis of sampling GrowlHelperApp (pid 53080) every 1 millisecond > Call graph: > 7866 Thread_25776971 DispatchQueue_1: com.apple.main-thread > (serial) > 7866 start > 7866 main > 7866 -[GrowlApplication run] > 7866 -[NSApplication run] > 7866 -[NSApplication > nextEventMatchingMask:untilDate:inMode:dequeue:] > 7866 _DPSNextEvent > 7866 BlockUntilNextEventMatchingListInMode > 7866 ReceiveNextEventCommon > 7866 RunCurrentEventLoopInMode > 7866 CFRunLoopRunSpecific > 7866 __CFRunLoopRun > 7866 > WebCore::MainResourceLoader::handleDataLoadNow(WebCore::RunLoopTimer<WebCore::MainResourceLoader>*) > 7866 > WebCore::MainResourceLoader::didReceiveResponse(WebCore::ResourceResponse > const&) > 7866 > WebCore::MainResourceLoader::continueAfterContentPolicy(WebCore::PolicyAction) > 7866 > WebCore::MainResourceLoader::continueAfterContentPolicy(WebCore::PolicyAction, > WebCore::ResourceResponse const&) > 7866 > WebCore::MainResourceLoader::didFinishLoading() > 7866 > WebCore::FrameLoader::finishedLoading() > 7866 > WebCore::FrameLoader::recursiveCheckLoadComplete() > 7866 > WebCore::FrameLoader::checkLoadCompleteForThisFrame() > 7866 > WebFrameLoaderClient::dispatchDidFinishLoad() > 7866 > CallFrameLoadDelegate(objc_object* (*)(objc_object*, > objc_selector*, ...), WebView*, objc_selector*, objc_object*) > 7866 - > [GrowlWebKitWindowController webView:didFinishLoadForFrame:] > 7391 - > [GrowlPositionController positionDisplay:] > 3914 > NSIntersectsRect > 3288 - > [GrowlPositionController positionDisplay:] > 189 NSContainsRect > 459 > dyld_stub_NSIntersectsRect > 16 > dyld_stub_NSContainsRect > 7866 Thread_25776973 DispatchQueue_2: com.apple.libdispatch- > manager (serial) > 7866 start_wqthread > 7866 _pthread_wqthread > 7866 _dispatch_worker_thread2 > 7866 _dispatch_queue_invoke > 7866 _dispatch_mgr_invoke > 7865 kevent > 1 _dispatch_run_timers > 1 _dispatch_wakeup > 1 _dispatch_queue_push_list_slow > 1 _dispatch_wakeup > 1 _dispatch_queue_push_list_slow > 1 _dispatch_wakeup > 1 _dispatch_queue_wakeup_global > 1 pthread_workqueue_additem_np > 1 pick_nextworkqueue_droplock > 1 __workq_kernreturn > 7866 Thread_25777012 > 7866 thread_start > 7866 _pthread_start > 7866 __NSThread__main__ > 7866 -[NSConnection run] > 7866 CFRunLoopRunSpecific > 7866 __CFRunLoopRun > 7866 mach_msg > 7866 mach_msg_trap > 7866 Thread_25777013 > 7866 thread_start > 7866 _pthread_start > 7866 __CFSocketManager > 7866 select$DARWIN_EXTSN > 7866 Thread_25777802: JavaScriptCore: FastMalloc scavenger > 7866 thread_start > 7866 _pthread_start > 7866 WTF::TCMalloc_PageHeap::runScavengerThread(void*) > 7866 WTF::TCMalloc_PageHeap::scavengerThread() > 7866 sleep > 7866 nanosleep > 7866 __semwait_signal > 7866 Thread_25777803 > 7866 thread_start > 7866 _pthread_start > 7866 __NSThread__main__ > 7866 +[NSURLConnection(NSURLConnectionReallyInternal) > _resourceLoadLoop:] > 7866 CFRunLoopRunSpecific > 7866 __CFRunLoopRun > 7866 mach_msg > 7866 mach_msg_trap > 7067 Thread_25880080 > 7067 start_wqthread > 7066 _pthread_wqthread > 7066 __workq_kernreturn > 1 start_wqthread > 799 Thread_25777794 > 799 start_wqthread > 799 _pthread_wqthread > 799 __workq_kernreturn > > Total number in stack (recursive counted multiple, when >=5): > > Sort by top of stack, same collapsed (when >= 5): > mach_msg_trap 15732 > __semwait_signal 7866 > __workq_kernreturn 7866 > select$DARWIN_EXTSN 7866 > kevent 7865 > NSIntersectsRect 3914 > -[GrowlPositionController positionDisplay:] 3288 > dyld_stub_NSIntersectsRect 459 > NSContainsRect 189 > dyld_stub_NSContainsRect 16 > > Piko > > On Jan 23, 9:58 pm, "Mr. Dashiell Michael Barlow" > <[email protected]> wrote: >> Heya >> >> Once again, had a Growl issue where I had Growl using 95+% of a >> processor core. This time, I had zero notifications up (as opposed to 1/3 of >> a 13" screen with smallish notifications) up, and more refused to show up, >> from Adium or iTunes (GrowlTunes). >> >> Process sample is attached. >> >> Stoping / Restarting from Growl prefpane had zero effect. Force quit >> from Activity Monitor on GrowlHelperApp and then a start from prefpane >> reversed my issue. (For the moment anyway). >> >> -- Dash >> >> ---- >> Signed, >> Mr. Dashiell Michael Barlow >> Life & Sanity > > -- > 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.
