http://bugs.winehq.org/show_bug.cgi?id=5774
------- Additional Comments From damjan.jov@gmail.com 2007-11-05 09:04 ------- The maximum value on that graph is 380, and assuming all the points are plotted, your maximum number of open files was <= 380. The maximum number of open files is at least 1024, so it wasn't maxed out when Kad went down, again confirming that this bug is not caused by a resource leak.
As far as netstat goes, UDP sockets never LISTEN (that's only for stream sockets like TCP), so all the netstat outputs I've seen on this page look perfectly normal. What I suspect happens, is that (for some reason) wine stops polling the socket, so emule no longer tries to receive any data. That would explain the large (and, I suspect, non-decreasing) receive queue in the nestat outputs when Kad breaks. I'll look over the logs this weekend and see whether that's what happens.
You can help by using wireshark to capture all UDP traffic from emule, and reporting whether there is any incoming/outgoing UDP from the Kad port after it dies. The Kad port number should be 4672, unless you've set it to be chosen randomly.