The CPU spike and potential crashes are a known issue, and unfortunately not resolved in the forthcoming 1.4, the problem is systemic to how the networking stack was designed, and as such is requiring it to be rewritten. Rudy has been working on this for quite awhile, trying to make sure the new networking stack is much more robust, and maintainable. Hopefully we will have it in a 1.4.1, or certainly in 2.0, which is otherwise almost ready for beta.
On May 31, 11:18 am, Petr Tichý <[email protected]> wrote: > FYI I'm having the same issue here, it looks like it happens after a > certain number of notifications. > > A sampling output is attached. > > Thanks for looking into that. > > Dne úterý, 29. května 2012 15:19:39 UTC+2 Dan Milne napsal(a): > > > > > > > > > > > I also have a crashing 1.3.3. CPU gets pegged at 100% - click on the > > growl icon and it crashes. I've attached a crash report. > > > On Monday, May 28, 2012 11:59:40 AM UTC+10, John Dalton wrote: > > >> Hi, > > >> I'm experiencing a recurring crash in Growl 1.3.3 on OSX 10.7.4. I have a > >> bunch of apps sending Growl notifications (including some via growlnotify > >> 1.3) and growl on this host is configured to forward notifications to a > >> laptop on the local network (which is often sleeping or otherwise > >> unavailable). > > >> Here's an excerpt of a crash log: > > >> Process: Growl [83420] > >> Path: /Applications/Growl.app/Contents/MacOS/Growl > >> Identifier: com.Growl.GrowlHelperApp > >> Version: 1.3.3 (1.3.3) > >> App Item ID: 467939042 > >> App External ID: 6097965 > >> Code Type: X86-64 (Native) > >> Parent Process: launchd [341] > > >> Date/Time: 2012-05-27 20:38:37.872 +1000 > >> OS Version: Mac OS X Server 10.7.4 (11E53) > >> Report Version: 9 > > >> Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > >> Exception Type: EXC_BAD_ACCESS (SIGSEGV) > >> Exception Codes: 0x000000000000000d, 0x0000000000000000 > > >> VM Regions Near 0: > >> --> > >> __TEXT 0000000101076000-00000001010e9000 [ 460K] > >> r-x/rwx SM=COW /Applications/Growl.app/Contents/MacOS/Growl > > >> Application Specific Information: > >> objc_msgSend() selector name: packetDidDisconnect: > >> objc[83420]: garbage collection is OFF > > >> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > >> 0 libobjc.A.dylib 0x00007fff9635de96 objc_msgSend + 22 > >> 1 com.Growl.GrowlHelperApp 0x00000001010b3379 > >> __33-[GCDAsyncSocket closeWithError:]_block_invoke_0 + 74 > >> 2 libdispatch.dylib 0x00007fff93e96a86 > >> _dispatch_call_block_and_release + 18 > >> 3 libdispatch.dylib 0x00007fff93e988f6 > >> _dispatch_main_queue_callback_4CF + 308 > >> 4 com.apple.CoreFoundation 0x00007fff93ff6e7c __CFRunLoopRun + > >> 1724 > >> 5 com.apple.CoreFoundation 0x00007fff93ff6486 > >> CFRunLoopRunSpecific + 230 > >> 6 com.apple.HIToolbox 0x00007fff90a2c4d3 > >> RunCurrentEventLoopInMode + 277 > >> 7 com.apple.HIToolbox 0x00007fff90a33781 > >> ReceiveNextEventCommon + 355 > >> 8 com.apple.HIToolbox 0x00007fff90a3360e > >> BlockUntilNextEventMatchingListInMode + 62 > >> 9 com.apple.AppKit 0x00007fff9781be31 _DPSNextEvent + 659 > >> 10 com.apple.AppKit 0x00007fff9781b735 -[NSApplication > >> nextEventMatchingMask:untilDate:inMode:dequeue:] + 135 > >> 11 com.apple.AppKit 0x00007fff97818071 -[NSApplication > >> run] + 470 > >> 12 com.Growl.GrowlHelperApp 0x000000010109a529 -[GrowlApplication > >> run] + 182 > >> 13 com.apple.AppKit 0x00007fff97a94244 NSApplicationMain > >> + 867 > >> 14 com.Growl.GrowlHelperApp 0x0000000101082625 main + 134 > >> 15 com.Growl.GrowlHelperApp 0x0000000101077924 start + 52 > > >> The crashes all appear to be happening in the same place. At a guess > >> something isn't dealing very well with the case where the connection is > >> lost (either between growl <-> app or growl <-> growl server (laptop)). > > >> It looks like someone else posted about this same issue on Jan 29th, but > >> there doesn't appear to be any resolution mentioned in that thread: > > >>https://groups.google.com/group/growldiscuss/browse_thread/thread/f24... > > >> I'm happy to provide any other details that may assist in tracking this > >> down and fixing it! > > >> Yours, > > >> John > > > > Vzorek procesu Growl.txt > 58KViewDownload -- 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.
