antp.be forum

I'm pretty sure there is a problem with sockets while obtaining information about large amount of movies over internet.

Windows crashed down claiming there is a problem with socket, wins tried restarting explorer.exe and then crashdown.

Maybe some stack is not cleared properly.

It is not me that made this code, I just use Indy library, which is used by hundreds of other programs.
Most of the times the problems are due to firewalls or proxy not properly configured. There isn't much that I can do.
The socket errors are just the raw error code returned by Windows. Each different code may be due to a completely different reason.

antp wrote:It is not me that made this code, I just use Indy library, which is used by hundreds of other programs.
Most of the times the problems are due to firewalls or proxy not properly configured. There isn't much that I can do.
The socket errors are just the raw error code returned by Windows. Each different code may be due to a completely different reason.

What is interesting - windows crashed obtaining socket for different application. I suppose sockets might stay open.

There is no reason of that. And even if it was the case, I do not see how an open connection would make other programs crash. I think that Windows often keeps connections open when they are not explicitly closed, and that do not crash (fortunately).
Btw if you use netstat tool in the console you can see open connections.
Are you sure that it is not a problem due to a firewall or something like that installed on your PC?

antp wrote:There is no reason of that. And even if it was the case, I do not see how an open connection would make other programs crash. I think that Windows often keeps connections open when they are not explicitly closed, and that do not crash (fortunately).
Btw if you use netstat tool in the console you can see open connections.
Are you sure that it is not a problem due to a firewall or something like that installed on your PC?

Wins crashed due to lack of resources (but all free). But while winsock was requesting a socket. I am not sure if it was due to Ant or firewall, but I think it has something to do with sockets.

I will keep an eye on it.