#7 Winsock fill-up Bug that makes MADDIS crash...

[Stefan Zickler]

We recently had a little bit of testing with MADDIS and
it turned out that after running it a little while it often
seems to crash with an "Automation Error" or
something similar.

Anyway, I was able to trace the root of the error in
terms of why it appears, but not the exact location in
the source that creates it.

The reason for the error is the following: Since MADDIS
supports several synchronous TCP-connections it
requires multiple instances of the MS Winsock-control.
This is achieved by using an array of winsocks.

To keep track of which of these winsocks are currently
unused there is another array:
"Public All_Sockets(1 To 32001) As Boolean"
in the module "damn_server_handler.bas"

when a winsock is in use, then the equivalent boolean
value in the array is set to true and if not then it's false.

Now the problem that occurs is that we somehow seem
to run out of winsocks which should not happen.

Usually when the close function is called on a winsock,
it should automatically clean all the connections and
set this array to false.

So the error is most likely ONE of the following:

1) I somewhere forgot to catch the closure of a tcp-
connection
2) The winsock object just "hangs up" in a busy state
even though there is no longer a TCP connection
3) I am unable to really unload or close the winsock
objects in some case.

This error should theoretically occur quicker if the
automatic subnet-scans are enabled.

I will appriciate help of some debuggers...or
comments/ideas, since I myself don't have a lot of time.