Re: [growl-discuss] Growl 2.0 causes the Mac Sonos Controller to crash

154 views
Skip to first unread message

Christopher Forsythe

unread,
Nov 5, 2012, 11:22:47 AM11/5/12
to growld...@googlegroups.com
Please contact Sonos support, and also please send us a crash log.

Chris

On Sun, Nov 4, 2012 at 2:47 AM, John Keys <jw....@googlemail.com> wrote:
The Sonos Controller, Version 3.8.2 (19.3.56060.97), starts up and displays "searching for your Sonos System" and promptly crashes if Growl is running.  I can post a crash dump if that would help. Not running Growl fixes the problem, the Sonos Controller runs fine. 

--
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/-/CWgf48qjkpgJ.
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

Daniel Siemer

unread,
Jan 9, 2013, 10:10:06 PM1/9/13
to Growl Discuss
They are using a fairly out of date version of Growl.framework (1.3),
in fact the class its crashing in doesn't even exist in the 2.0
framework. Can you try running Growl Version Detective (available
here http://growl.info/downloads#generaldownloads) and on the
framework tab, finding Sonos.app and hitting the Upgrade FW button to
upgrade to the 2.0 framework. GVD moves the older framework aside so
that if the new framework makes things even worse in some way, you can
revert to the 1.3 one later.

On Jan 9, 5:35 pm, Garrett Bentley <gbentley...@gmail.com> wrote:
> Hello:
> I contacted Sonos and they are escalating the issue to Tier 2 support.
>  Anyways, I've attached a crash log.  The issue is here:
>
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0   com.apple.CoreFoundation       0x938a68c0 CFRelease + 48
> 1   com.growl.growlframework       0xc001cbed +[GrowlGNTPPacket
> addSentAndReceivedHeadersFromDict:toArray:] + 78
> 2   com.growl.growlframework       0xc001d8ab +[GrowlRegisterGNTPPacket
> getHeaders:andBinaryChunks:forRegistrationDict:] + 1252
> 3   com.growl.growlframework       0xc0018db5 +[GrowlGNTPOutgoingPacket
> outgoingPacketOfType:forDict:] + 512
> 4   com.growl.growlframework       0xc0009eb9
> -[GrowlGNTPRegistrationAttempt packet] + 71
> 5   com.growl.growlframework       0xc000a3a9
> -[GrowlGNTPCommunicationAttempt socket:didConnectToHost:port:] + 36
> 6   com.growl.growlframework       0xc00105e6 __29-[GCDAsyncSocket
> didConnect:]_block_invoke_0 + 106
>
> Please let me know your thoughts.
>
> Thanks,
> Garrett
>
>
>
>
>
>
>
> On Monday, November 5, 2012 9:22:50 AM UTC-7, Christopher Forsythe wrote:
>
> > Please contact Sonos support, and also please send us a crash log.
>
> > Chris
>
> > On Sun, Nov 4, 2012 at 2:47 AM, John Keys <jw....@googlemail.com<javascript:>
> > > wrote:
>
> >> The Sonos Controller, Version 3.8.2 (19.3.56060.97), starts up and
> >> displays "searching for your Sonos System" and promptly crashes if Growl is
> >> running.  I can post a crash dump if that would help. Not running Growl
> >> fixes the problem, the Sonos Controller runs fine.
>
> >> --
> >> 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/-/CWgf48qjkpgJ.
> >> To post to this group, send email to growld...@googlegroups.com<javascript:>
> >> .
> >> To unsubscribe from this group, send email to
> >> growldiscuss...@googlegroups.com <javascript:>.
> >> For more options, visit this group at
> >>http://groups.google.com/group/growldiscuss?hl=en.
>
> > --
> > Chris Forsythe
> > @The_Tick <http://twitter.com/The_Tick>
>
>
>
>  SonosMCR Crash Report.rtf
> 52KViewDownload

Garrett Bentley

unread,
Jan 9, 2013, 10:32:17 PM1/9/13
to growld...@googlegroups.com
Hello:
Thank you for your response.  Upgrading the framework to version 2.0 worked perfectly.  There are no more crashes.  I e-mailed Sonos and told them about this fix (and this forum) so hopefully it's fixed for everyone soon!

Thanks again,
Garrett
Reply all
Reply to author
Forward
0 new messages