growlnotify still intermittently drops messages

[GoogleCodeExporter]

http://forums.cocoaforge.com/viewtopic.php?p=109764#p109764:

> This thread seems to describe almost the same problem that I'm having using
> Growl 1.1.4, growlnotify, and Leopard 10.5.4:
>
> - Executing <growlnotify -m "hello"> fires a notification 100% of the time.
> - Executing <growlnotify -m "hello" --image 
/Users/ed_ruder/Dev/Rails/pass.png>
> fires intermittently. It *seems* that the quicker I execute the growlnotify
> lines, the more dropped notifications occur. As far as I can tell, whenever a
> notification fails to fire, I see the following in system.log:
>
> GrowlHelperApp[5247]: *** -[NSMachPort handlePortMessage:]: dropping incoming 
DO
> message because the connection or ports are invalid

At least one message after that indicates that this problem does still exist in 
growlnotify 1.1.4.

Original issue reported on code.google.com by chrisf.g...@gmail.com on 6 Dec 2009 at 1:26

[GoogleCodeExporter]

Confirming this behavior with grownotify 1.2 and Mac OS 10.5.8.

'repeat 10 growlnotify -m test --image some_image' is usually sufficient to
reproduce. (Less than 10 notifications are posted and same console message.)

Looking forward to fix.

Original comment by bug.me.not.dude@googlemail.com on 15 Feb 2010 at 7:59

[GoogleCodeExporter]

Where is repeat on your file system?

Original comment by chrisf.g...@gmail.com on 16 Feb 2010 at 2:07

[GoogleCodeExporter]

Oops. repeat is a (t)csh builtin, so you can't reproduce with (ba)sh.

Original comment by bug.me.not.dude@googlemail.com on 20 Feb 2010 at 3:25

[GoogleCodeExporter]

Ah, I forgot about that. That's what I get for switching to bash.

Confirmed it. First time, it fired 3. The next, it fired 7. Tried multiple 
times, never saw 10.

2/19/10 10:13:42 PM GrowlHelperApp[46494] *** -[NSMachPort handlePortMessage:]: 
dropping incoming DO 
message because the connection or ports are invalid 

For every entry that doesn't occur, I am seeing this in the console. I think 
maybe this explains it. Perhaps the 
change to gntp will change this behavior, in which case we may see a fix in 1.3.

2/19/10 10:21:36 PM GrowlHelperApp[46494] *** NSDistantObject initWithCoder: 
0x48 not given away for 
conn 0x12e120 

I also saw this, I'm not sure why yet.

This is all in 1.2

Original comment by chrisf.g...@gmail.com on 20 Feb 2010 at 4:24

[GoogleCodeExporter]

Original comment by chrisf.g...@gmail.com on 20 Feb 2010 at 3:18

• Added labels: Milestone-1.3

[GoogleCodeExporter]

Original comment by chrisf.g...@gmail.com on 29 Jul 2010 at 4:43

• Added labels: Milestone-2.0

[GoogleCodeExporter]

The change to GNTP in GrowlNotify means the cause of this problem is gone.  

Original comment by dan...@growl.info on 14 Sep 2011 at 9:04

• Changed state: FixedInSource

[GoogleCodeExporter]

Growl 2 is released, marking these as fixed.

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