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
@The_Tick (http://twitter.com/The_Tick)


On Friday, June 15, 2012 at 2:11 AM, Chris Forsythe wrote:

> Hi Peter, 
> 
> First, we have a development list:
> 
> https://groups.google.com/forum/?fromgroups#!forum/growl-development
> 
> 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
> @The_Tick (http://twitter.com/The_Tick)
> 
> 
> 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
> > > @The_Tick (http://twitter.com/The_Tick)
> > > 
> > > 
> > > 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.
> > To post to this group, send email to [email protected] 
> > (mailto:[email protected]).
> > To unsubscribe from this group, send email to 
> > [email protected] 
> > (mailto:[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