http://bugs.winehq.org/show_bug.cgi?id=3063
felix.nawothnig@t-online.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1
------- Additional Comments From felix.nawothnig@t-online.de 2005-21-06 10:50 ------- Confirmed - I've been encountering the same problem. As a workaround you can do a) decrease the hard-limit of connections in eMule and b) increase the max open fds with ulimit -n.
As those workarounds only seem to delay the crash and eMule runs fine on Windows it seems Wine and not eMule is leaking here - and this "wine client error" should probably not happen in any case...