We're hoping to have 1.4 out soon, but I don't have an exact date. -- Chris Forsythe
On Saturday, April 7, 2012 at 4:18 PM, Roman Revyakin wrote: > A small update from me: I was wrong about the fix of the issue by upgrading > Skype to 5.6: after I updated the framework to Growl 1.3.1 in Skype, the > undying connections came back again. > > Chris, could you tell if there is any ETA on when the 1.4 gets released? > > On Sat, Apr 7, 2012 at 9:43 PM, Eduardo Habkost <[email protected] > (mailto:[email protected])> wrote: > > Hi, Chris, > > When it gets released, will the fix require updating the client framework > > on the apps, or just updating Growl? > > -- > > Eduardo > > On Apr 7, 2012 2:39 AM, "Chris Forsythe" <[email protected] > > (mailto:[email protected])> wrote: > > > The high cpu issue is something we're tracking down and working on fixing > > > for 1.4. It's taken so long since we finally figured out the root cause > > > very very recently. The fix is unfortunately going to take a bit longer, > > > especially since we're doing additional testing to make sure that > > > everything works right. The good news is now that we know the root cause, > > > that's half the battle. :) > > > > > > -- > > > Chris Forsythe > > > > > > > > > On Friday, April 6, 2012 at 9:18 PM, Roman Revyakin wrote: > > > > > > > Found an advice in a separate thread to update my version of Skype: > > > > > > > > https://groups.google.com/forum/?fromgroups#!topic/growldiscuss/ekGV6Striyo > > > > > > > > > > > > (somehow I assumed I would be notified of an update but I was not). > > > > Now running Skype version 5.6.0.203 (was 5.5.3.xx before) and do not > > > > see so far any constant increase in connections to Growl. Will see what > > > > happens when I leave it running for a while. > > > > > > > > On Wed, Apr 4, 2012 at 2:07 PM, Roman Revyakin > > > > <[email protected] (mailto:[email protected])> wrote: > > > > > Update: if I set Growl to display the "... went online" "...went > > > > > offline" notifications, then there is no connection leak on Growl > > > > > side experienced any longer. > > > > > > > > > > > > > > > On Wed, Apr 4, 2012 at 1:33 PM, Roman Revyakin > > > > > <[email protected] (mailto:[email protected])> wrote: > > > > > > And yeah, there are no notifications settings for "Contact comes > > > > > > online" inside Skype itself, and I was talking about those ones > > > > > > popping up whenever Growl dies, not the "Contact becomes > > > > > > available". > > > > > > They are in Growl preferences though and I have them disabled. > > > > > > So, in short - it might be the same problem as with Adium, only I > > > > > > cannot work around it. > > > > > > > > > > > > > > > > > > On Wed, Apr 4, 2012 at 1:29 PM, Roman Revyakin > > > > > > <[email protected] (mailto:[email protected])> wrote: > > > > > > > In case of Skype, when I choose to use "Growl" notifications > > > > > > > instead of "Built-in", all of its internal preferences for > > > > > > > showing the notification become greyed out, so it is impossible > > > > > > > to check or uncheck them. > > > > > > > I tried to bring inline the preferences and start running Skype > > > > > > > again using Growl with no effect on the connections to Growl > > > > > > > (after a while they accumulated to 165 again), so I am thinking > > > > > > > of turning off Skype sending notifications through Growl, rather > > > > > > > using the built-in notifier. > > > > > > > I will be definitely missing out on the Growl history, I know. > > > > > > > Interestingly, I have had the "Contact becomes available" in > > > > > > > Skype preferences disabled, but I noticed that once Growl dies, > > > > > > > Skype begins to display those notifications through its own > > > > > > > built-in Growl notifier. > > > > > > > > > > > > > > On Wed, Apr 4, 2012 at 8:23 AM, Eduardo Habkost > > > > > > > <[email protected] (mailto:[email protected])> wrote: > > > > > > > > Note that in the case of Adium, I have noticed the bug only > > > > > > > > because one notification type ("Contact signs on") was enabled > > > > > > > > on my Adium preferences, but disabled on my Growl preferences. > > > > > > > > > > > > > > > > After I disabled the notification on Adium itself, I stopped > > > > > > > > seeing the bug. That happened because (on my case), connections > > > > > > > > were kept open only when Adium got "the user disabled this > > > > > > > > notification" error responses. > > > > > > > > > > > > > > > > -- > > > > > > > > Eduardo > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, April 3, 2012 at 19:11 , Roman Revyakin wrote: > > > > > > > > > > > > > > > > > Where does one download Growl Betas? > > > > > > > > > Do you use something like Skype or Adium which usually > > > > > > > > > produce a lot of messages so that one can test the undying > > > > > > > > > connections? > > > > > > > > > > > > > > > > > > On Tue, Apr 3, 2012 at 1:12 AM, joelw135 <[email protected] > > > > > > > > > (mailto:[email protected]) (mailto:[email protected])> wrote: > > > > > > > > > > After starting GROWL new Beta I had using command lsof -i > > > > > > > > > > :23053 | cut > > > > > > > > > > -d' ' -f1 | sort | uniq -c > > > > > > > > > > 1 Command > > > > > > > > > > 5 GROWL > > > > > > > > > > After 1/2 hour it was > > > > > > > > > > 1 Command > > > > > > > > > > 14 GROWL > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > 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] > > > > > > > > (mailto:[email protected]). > > > > > > > > To unsubscribe from this group, send email to > > > > > > > > [email protected] > > > > > > > > (mailto:growldiscuss%[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] > > > > (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] > > > (mailto:[email protected]). > > > To unsubscribe from this group, send email to > > > [email protected] > > > (mailto:growldiscuss%[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] > > (mailto:[email protected]). > > To unsubscribe from this group, send email to > > [email protected] > > (mailto:growldiscuss%[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] > (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.
