Crash+rejaunch = port binding error

[Harold]

Apparently because the new process starts too fast for the old (crashed) one to close.

Just in case it matters, it's the kind of crash that happens when coming out of stand-by mode.

That's a perfectly valid reason to crash and I'm not complaining, but it's a bit annoying that I have to relaunch µT manually (which I have to, because of the port binding error).

[Firon]

Are you running 1.8.2?

[Harold]

Yes

It's not new though, it also happened in earlier versions (but I'm not sure how far back it goes)

[Ultima]

Windows simply isn't releasing the port quickly enough, I guess. It's been happening since forever.

[Harold]

So, if I may make a suggestion, retry to bind to the port again about 1 or 2 seconds later?

[Ultima]

Sometimes, if Windows doesn't release the port properly, it doesn't release for a long time. I've seen it happen across multiple restarts of µTorrent, and it was sometimes only solved with a computer restart (or a very long wait, on the order of minutes). The cause of the problem is probably deeper still. Could be a firewall or network card driver, I don't know.

At any rate, I don't really see anything really wrong with that request (assuming µTorrent logically decides when to stop attempting).