Hangs after the first network forwarded notification

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Enable password protected network notifications
2. After first notification is sent, the sending Growl is frozen
3.

I have two machines, A (with 10.5) and B (with 10.6) (both Intel). I have
enabled password protected network notifications on both of them.

My problem is that after B received the first notification from A, A stops
to notify, both locally and remotely. Stopping Growl from the menu bar icon
does not stop it, I have to manually kill the GrowlHelperApp process (kill
is enough, -9 is not required).

Using Growl 1.2 and it is mostly Adium notifications I try to forward.

What is the expected output?

What do you see instead?

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

Please provide any additional information below.

Original issue reported on code.google.com by dbo...@gmail.com on 26 Apr 2010 at 8:47

[GoogleCodeExporter]

Some further details:

1. after disabling forwarding of notifications on B, B started to receive
notifications from A in a predictable and stable manner.

2. I then tried to

a. delete all preferences etc related to Growl on A in my home library (I found 
a
cache file, a preference file and some tickets)

b. disabling network forwarding on A while I enabled it on B

but the result didn't change, GrowlHelperApp still freezes.

When I click Stop in the prefpane GrowlHelperApp remains "running" (but not
responding), I have to kill (-9 is not necessary) it manually to stop it. The 
freeze
happens soon after start, within a minute or two.

Currently I just try to forward notifications from Adium, Last FM and 
iScrobbler (yes
I run both Last FM and iScrobbler on B) from B to A. All these notifications are
displayed as expected on B.

% telnet localhost 23052
% nmap -p 9887 -v -sU localhost

both work as expected and don't causes the GrowlHelperApp to freeze. It is only 
when
B sends something to A the freeze occur. Does B send invalid data?

This is the result from "inspecting" and the list the open ports and files for 
the
GrowlHelperApp process in Activity Monitor when it is frozen:

/
/Library/PreferencePanes/Growl.prefPane/Contents/Resources/GrowlHelperApp.app/Co
ntents/MacOS/GrowlHelperApp
/System/Library/Frameworks/PreferencePanes.framework/Versions/A/PreferencePanes
/Library/InputManagers/SIMBL/SIMBL.bundle/Contents/MacOS/SIMBL
/Volumes/maxi/Users/db/Library/Application
Support/SIMBL/Plugins/megazoomer.bundle/Contents/MacOS/megazoomer
/private/var/tmp/mds/messages/se_SecurityMessages
/usr/share/icu/icudt36l.dat
/System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
/Library/Caches/com.apple.LaunchServices-023501.csstore
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fram
ework/Versions/A/Resources/Extras2.rsrc
/usr/lib/dyld
/private/var/db/dyld/dyld_shared_cache_i386
/dev/null

*:23052
->0x843d5d8
->0xb781660
->0xb781000
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fram
ework/Versions/A/Resources/Extras2.rsrc
192.168.1.65:23052->192.168.1.76:50276

Don't know if this is relevant. Let me know if I can do anything else to 
resolve this
problem.

Original comment by dbo...@gmail.com on 13 May 2010 at 6:04

[GoogleCodeExporter]

closing as wontfix since legacy networking will not be included in the next 
major release of Growl.

Original comment by rarich...@gmail.com on 9 Jul 2010 at 3:16

• Changed state: WontFix