#27 UT doesn't release network when crashing

[Jamison Stepan]

Sometimes when I get a hard crash on UT, when in the process of connecting to a remote server, UT doesn't release the network. I continue to get packets even though the client is dead. Here's a tcpdump of the packets that are being sent:
22:44:31.276796 209.10.133.85.7817 > jstepan.dsl.scc.net.1026: udp 2
22:44:31.512630 209.10.133.85.7817 > jstepan.dsl.scc.net.1026: udp 2
22:44:31.746514 209.10.133.85.7817 > jstepan.dsl.scc.net.1026: udp 2
22:44:31.981045 209.10.133.85.7817 > jstepan.dsl.scc.net.1026: udp 2
22:44:31.981114 jstepan.dsl.scc.net > 209.10.133.85: icmp: jstepan.dsl.scc.net udp port 1026
unreachable [tos 0xc0]

Running UT on Mandrake 6.1, Voodoo3 2000, 128MB memory.

[Nobody/Anonymous]

Well if network was not released ( meaning program was still bound to udp ports ), then the last message of your tcp dump wouldn\'t be there.

What are those incoming udp packets you may ask.
I _think_ (i\'m just a [g|l]amer) that UT servers have some
timeout value, until then they still send the game info or beacon or whatever. I have these incoming udp packets on clean exits from the program and after a time they die out.

[Jamison Stepan]

Thanks. I was assuming it was a timeout issue, I guess I just never checked after a clean exit. I wonder what kind of overhead this adds to the server to not be releasing it\'s connection right away? Should the timeout be shorter so that things don\'t hang on as long?