Re: [growl-discuss] Got disconnected: Error

183 views
Skip to first unread message

Chris Forsythe

unread,
Jun 9, 2012, 12:33:31 PM6/9/12
to growld...@googlegroups.com
Hey update to Growl 1.4 and tell us what you are seeing.

Also, does the notification go through?

-- 
Chris Forsythe

On Saturday, June 9, 2012 at 7:39 AM, Nacho Caballero wrote:

I'm using growlnotify inside a loop on ruby script and I keep getting these errors:
2012-06-09 08:33:59.770 growlnotify[50474:f07] Got disconnected: Error Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out" UserInfo=0x7fdcab420330 {NSLocalizedDescription=Read operation timed out}

I have Growl 1.3.3 installed and growlnotify 1.3

This is my ruby code:
def rest
    system %[growlnotify -sw "Blink\!" -m "It's about time"]
    print "Rest!\r"
    $stdout.flush
    sleep 20
    system %[afplay #{BELL_PATH}]
end

Any ideas?

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/8aYK1q-PHo8J.
To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.

Chris Forsythe

unread,
Jun 15, 2012, 5:11:37 AM6/15/12
to growld...@googlegroups.com
Hi Peter,

First, we have a development list:


Next, you can send the crash logs, I would expect that's what we would need to see. We have our support contact information listed on our contact page if you want them working with us directly, but since you've contacted us I'm going to assume that you want to handle that. I'd recommend asking the user to send the crash report to you, and then for you to show us the trace on the crashed thread(s). You can contact me directly if you want to do something else, but this seems like the easiest thing to me.

-- 
Chris Forsythe

On Friday, June 15, 2012 at 12:57 AM, Peter Lewis wrote:

I just updated the Growl API in the latest Keyboard Maestro beta to 1.3.1 (to avoid a 160MB memory leak on every growl message!).  But the first day of user testing I have a report of Growl 1.4 crashing and this Got disconnected console messages:

12.06.15 14:04:16.706 Keyboard Maestro Engine: <GrowlGNTPNotificationAttempt: 0x1093423b0> failed because Error Domain=GCDAsyncSocketErrorDomain Code=7 "Socket closed by remote peer" UserInfo=0x109305da0 {NSLocalizedDescription=Socket closed by remote peer}
12.06.15 14:04:16.707 Keyboard Maestro Engine: <GrowlGNTPNotificationAttempt: 0x10bde6500> failed because Error Domain=GCDAsyncSocketErrorDomain Code=7 "Socket closed by remote peer" UserInfo=0x109305e90 {NSLocalizedDescription=Socket closed by remote peer}
12.06.15 14:04:16.707 Keyboard Maestro Engine: <GrowlGNTPNotificationAttempt: 0x103b25ec0> failed because Error Domain=GCDAsyncSocketErrorDomain Code=7 "Socket closed by remote peer" UserInfo=0x109309980 {NSLocalizedDescription=Socket closed by remote peer}
12.06.15 14:04:19.127 ReportCrash: Saved crash report for Growl[3382] version 1.4 (1.4) to /Users/xxxx/Library/Logs/DiagnosticReports/Growl_2012-06-15-140419_MacBook-Pro.crash

That is not an auspicious start to 1.3.1 SDK and 1.4!

Any advice.  Where should I ask the user to email the crash report (and please don't ask me to ask them to sign up to some forum or use some web reporting tool please, I wouldn't do that to my customers).

Thanks,
   Peter.


On Sunday, 10 June 2012 00:33:31 UTC+8, Christopher Forsythe wrote:
Hey update to Growl 1.4 and tell us what you are seeing.

Also, does the notification go through?

-- 
Chris Forsythe

On Saturday, June 9, 2012 at 7:39 AM, Nacho Caballero wrote:

I'm using growlnotify inside a loop on ruby script and I keep getting these errors:
2012-06-09 08:33:59.770 growlnotify[50474:f07] Got disconnected: Error Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out" UserInfo=0x7fdcab420330 {NSLocalizedDescription=Read operation timed out}

I have Growl 1.3.3 installed and growlnotify 1.3

This is my ruby code:
def rest
    system %[growlnotify -sw "Blink\!" -m "It's about time"]
    print "Rest!\r"
    $stdout.flush
    sleep 20
    system %[afplay #{BELL_PATH}]
end

Any ideas?


--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/8RkizGF9lUAJ.

Chris Forsythe

unread,
Jun 15, 2012, 5:12:28 AM6/15/12
to growld...@googlegroups.com
Also, we're all at WWDC and will be traveling throughout the weekend so just a heads up that responding will be hit or miss until we're on better wifi.

-- 
Chris Forsythe

Peter Lewis

unread,
Jun 15, 2012, 6:02:50 AM6/15/12
to growld...@googlegroups.com
On Friday, 15 June 2012 17:11:37 UTC+8, Christopher Forsythe wrote:
First, we have a development list:


Ahh - I just followed the links from your Report a Bug page <http://growl.info/reportabug.php> which leads says "the best way to report it is to send an email to our discussion list ".  Since we're here now, I'll continue here, at least to finish this report.

Next, you can send the crash logs, I would expect that's what we would need to see. We have our support contact information listed on our contact page if you want them working with us directly, but since you've contacted us I'm going to assume that you want to handle that. I'd recommend asking the user to send the crash report to you, and then for you to show us the trace on the crashed thread(s). You can contact me directly if you want to do something else, but this seems like the easiest thing to me.

Here is the relevant section of the crash log:

Process:         Growl [3382]
Path:            /Applications/Growl.app/Contents/MacOS/Growl
Identifier:      com.Growl.GrowlHelperApp
Version:         1.4 (1.4)
App Item ID:     467939042
App External ID: 8236495
Code Type:       X86-64 (Native)
Parent Process:  launchd [159]

Date/Time:       2012-06-15 14:04:10.982 +0900
OS Version:      Mac OS X 10.7.4 (11E53)
Report Version:  9

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
objc[3382]: garbage collection is OFF
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib         0x00007fff9112ece2 __pthread_kill + 10
1   libsystem_c.dylib              0x00007fff922517d2 pthread_kill + 95
2   libsystem_c.dylib              0x00007fff92242a7a abort + 143
3   com.apple.HIToolbox            0x00007fff9198760f TTheme::GetCurrent() + 167
4   com.apple.HIToolbox            0x00007fff919b1435 DataEngine::GetMenuSeparatorHeight(short&) + 29
5   com.apple.HIToolbox            0x00007fff919b1273 HIStandardMenuView::HIStandardMenuView(OpaqueHIObjectRef*) + 349
6   com.apple.HIToolbox            0x00007fff919b110c HIStandardMenuView::Construct(OpaqueHIObjectRef*) + 34
7   com.apple.HIToolbox            0x00007fff9197d2a8 HIView::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 160
8   com.apple.HIToolbox            0x00007fff9195d2bb HIObject::Construct(HIObjectClass*, HIObject**, OpaqueHIObjectRef*) + 121
9   com.apple.HIToolbox            0x00007fff9195cf55 HIObject::Create(__CFString const*, OpaqueEventRef*, HIObject**) + 201
10  com.apple.HIToolbox            0x00007fff9195ce70 HIObjectCreate + 90
11  com.apple.HIToolbox            0x00007fff919b0edf MenuData::CreateMenuContentView() + 159
12  com.apple.HIToolbox            0x00007fff919b0e30 MenuData::GetModalView() + 32
13  com.apple.HIToolbox            0x00007fff91ae9ef4 _CalcMenuSizeOnDevice(MenuData*, unsigned short, unsigned int, CGRect const*, unsigned int) + 651
14  com.apple.AppKit               0x0000000107df6445 -[NSCarbonMenuImpl _maximumSizeForScreen:] + 87
15  com.apple.AppKit               0x0000000107f6972b -[NSMenu size] + 35
16  com.apple.AppKit               0x000000010805b563 +[NSStatusBarButtonCell popupStatusBarMenu:inRect:ofView:withEvent:] + 422
17  com.apple.AppKit               0x000000010805d60c -[NSStatusItem popUpStatusItemMenu:] + 160
18  com.Growl.GrowlHelperApp       0x00000001075df750 -[GrowlMenuImageView mouseDown:] + 101
19  com.apple.AppKit               0x0000000107ba7348 -[NSWindow sendEvent:] + 6306
20  com.apple.AppKit               0x000000010805c31c -[NSStatusBarWindow sendEvent:] + 66
21  com.apple.AppKit               0x0000000107b40a55 -[NSApplication sendEvent:] + 5593
22  com.apple.AppKit               0x0000000107ad70c6 -[NSApplication run] + 555
23  com.Growl.GrowlHelperApp       0x00000001075b7beb -[GrowlApplication run] + 182
24  com.apple.AppKit               0x0000000107d53244 NSApplicationMain + 867
25  com.Growl.GrowlHelperApp       0x000000010759e18c main + 134
26  com.Growl.GrowlHelperApp       0x0000000107596124 start + 52

I hope that proves useful.  The customer said they got the "Got disconnected" console log twice, but only once got the crash.  Certainly if Growl crashes, I would not be surprised by a disconnection error in the console.

Enjoy WWDC - it's been many years since I was last there.
   Peter.
Reply all
Reply to author
Forward
0 new messages