search

brettpoole / growl

Automatically exported from code.google.com/p/growl
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Growl crash in network receive, possibly framework related. #336

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. I have just been using the iMac found no apparent reason.

What is the expected output?

No output expected

What do you see instead?

Growl not crashing

What version of the product are you using? On what operating system?

Growl Version 1.3, OSX 10.7.2 6GB Ram iMac Hardware Growler 1.2b2.

Please provide any additional information below.

Original issue reported on code.google.com by j...@waxman.org on 21 Oct 2011 at 5:49

Attachments:

GoogleCodeExporter commented 8 years ago 
So based on where it crashed, I need a bit more info, since we use 
GCDAsyncSocket for incoming and outgoing notes (and their respective replies), 
and for the new framework. 

Are you using network forwarding, or receiving incoming notifications from 
another computer?  If so, please describe how you have this setup.  
Also, are you using the 1.3 Framework anywhere, as it also can use networking 
to talk to Growl.

Original comment by dan...@growl.info on 21 Oct 2011 at 6:18

GoogleCodeExporter commented 8 years ago 
Yes I am using network forwarding from the iMac to my MacBook Pro and from the 
MacBook Pro to the iMac. The crash is on the iMac. I am using Hardware Growler 
Beta 2 with the 1.3 framework.

Original comment by j...@waxman.org on 21 Oct 2011 at 6:23

GoogleCodeExporter commented 8 years ago 
If you can, please try to narrow down whether its from Growl.app receiving 
notes (ie, from HWGrowler or the MBP), or from sending notes (ie, to the MBP).  
If it is receiving notes, in theory it should the same whether its HWGrowler or 
the MBP sending them, but if you can also try eliminating one or the other of 
them, it would also be helpful.

Original comment by dan...@growl.info on 21 Oct 2011 at 6:43

GoogleCodeExporter commented 8 years ago 
It has to be the iMac sending alerts as the MacBook Pro was OFF at the time. I 
already stopped the network connections on the iMac for now, and might end up 
doing so on the MacBook.  My original idea was to use the network alerts while 
out of the office to monitor the iMac, but I am getting way to many alerts of 
non importance cutting down on my work time.

Original comment by j...@waxman.org on 21 Oct 2011 at 6:48

GoogleCodeExporter commented 8 years ago 
That actually helps narrow it down, however, the iMac crashing at 
"completeCurrentRead" with the MBP off actually points at something using the 
Growl 1.3 framework, and you cant read a network message from something that is 
off, much less send something to it.  

Setting to 1.3.1, but no promises that I will find it in time, as there are a 
number of other critical fixes that need to ship.  

As for the second point, we plan to address forwarding all or nothing at some 
point in the future, and Im pretty sure theres already a ticket for that 
someplace.

Original comment by dan...@growl.info on 22 Oct 2011 at 2:41

GoogleCodeExporter commented 8 years ago

Original comment by ch...@growl.info on 31 Oct 2011 at 2:56

GoogleCodeExporter commented 8 years ago

Original comment by ch...@growl.info on 19 Jan 2012 at 10:11

GoogleCodeExporter commented 8 years ago 
This should all hopefully be resolved with 2.0's new stack

Original comment by dan...@growl.info on 16 Jul 2012 at 8:20

GoogleCodeExporter commented 8 years ago 
Closing this. If it occurs once 2.0 is out, reopen it.

Original comment by ch...@growl.info on 27 Aug 2012 at 1:34

GoogleCodeExporter commented 8 years ago 
Growl 2 is released, marking these as fixed.

Original comment by ch...@growl.info on 20 Sep 2012 at 3:16

GoogleCodeExporter commented 8 years ago

Original comment by ch...@growl.info on 11 Jan 2013 at 6:27