search

PhilMurwin / growl-for-windows

Automatically exported from code.google.com/p/growl-for-windows
0 stars 0 forks source link

Growl.exe doesnt close its sockets properly #21

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run growl.exe
2. Run visual studio growl plugin
3. Do a few builds to force growl to show a notification
4. Do a netstat or use tcpview to view half-open sockets

Observe that growl.exe is holding on to CLOSE_WAIT sockets

I am using growl for windows V2.0 (build 2.0.0.25) on windows xp service pack 3

Original issue reported on code.google.com by andrewke...@gmail.com on 9 Dec 2009 at 2:51

Attachments:

GoogleCodeExporter commented 9 years ago 
thanks for reporting this. it is a known issue and is fixed in local dev 
builds. the
fix will be released in the next version of GfW, though no timeline is defined 
yet.

Original comment by briandun...@gmail.com on 9 Dec 2009 at 5:42

GoogleCodeExporter commented 9 years ago 
Is this defect present in GfW version 1 ? Should i downgrade in the meantime 
whilst i wait 
for the next version ?

Original comment by andrewke...@gmail.com on 9 Dec 2009 at 9:56

GoogleCodeExporter commented 9 years ago 
this defect is present in all versions to date. you can grab a pre-release 
version
that contains the fix from this thread:
http://groups.google.com/group/growl-for-windows/browse_thread/thread/7294fea01f
c33444

Original comment by briandun...@gmail.com on 10 Dec 2009 at 2:25

GoogleCodeExporter commented 9 years ago 
GfW V 2.0.1b1 (build 2.0.0.26) seems to have fixed this problem :). Thanks :)

Original comment by andrewke...@gmail.com on 10 Dec 2009 at 4:19

GoogleCodeExporter commented 9 years ago 
Hello,

My problem seems similar to this one.
I've got the last version 2.0.0.27 available on the website.

I can send local notification unless i do not use sockets.
Example:
I try to send some notification via growlnotify or "growl for firefox". It works
perfectly.
But when i try to send some notifications over the network, nothing happens and 
it is
then impossible to send local notifications anymore.
I have to restart growl for everything to work.

Original comment by bendec...@gmail.com on 2 Jan 2010 at 5:27

GoogleCodeExporter commented 9 years ago 
@bendecall - that definitely sounds like a bug, but i am not sure it is related 
to
the original post. (that issue didnt affect the operation of GfW, just leaked 
sockets
behind the scenes).

i will try to take a look at your specific problem to see if i can figure 
anything
else out. any additional details or specific information would be much 
appreciated.

Original comment by briandun...@gmail.com on 4 Jan 2010 at 5:22

GoogleCodeExporter commented 9 years ago 
As i said, i've got the last growl build. I'm on Windows XP. The other computer 
used
to send notification is on the same local network and runs windows XP with the 
last
version of growl as well.
I'm gonna try with another computer in a few days to see which computer causes 
the
problem. The one that receives the notifications i guess. I'll also have a look 
at
tcpview.

It sounds like the socket used by local applications is unavailable after been 
used
on the network...

Original comment by bendec...@gmail.com on 8 Jan 2010 at 3:42

GoogleCodeExporter commented 9 years ago 
i havent had any more reports of this behavior for several versions. can you 
confirm if you are still seeing this issue? if not, i will mark this issue as 
closed. thanks.

Original comment by briandun...@gmail.com on 17 Jun 2010 at 4:12

GoogleCodeExporter commented 9 years ago 
no additional reports of this, so i am closing this issue. feel free to 
reopen/resubmit if the behavior persists.

Original comment by briandun...@gmail.com on 27 Aug 2010 at 6:09