linuxdcpp-team team mailing list archive
-
linuxdcpp-team team
-
Mailing list archive
-
Message #04560
[Bug 837544] Re: Handles trapped on closing socket
well ...
Rev527 compiled with mingw 4.5.2 works like a dream , a clean start uses
around 70 handles, with all scripts loaded including pxbridge.
Same Rev compiled with 4.6.1 acts completely different, if you use it pure core (no scripts loaded) it uses also around 70 handles but ...
as soon you load the scripts the scripts it go's to 200+ without any users , and every joining user is consuming a lot of handles.
To compere a 4.5.2 with 20 users uses like 100, a 4.6.1 go's to 400 and
even far above that when a op with a lot of ucmd's joins.
The exesive handles are not trapped , they seem freed when the "clearing
pool" runs but it still uses like 10 times more handles then the 4.5.2
compile :)
--
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/837544
Title:
Handles trapped on closing socket
Status in ADCH++:
Invalid
Bug description:
Rev 519 tryed on both XP and Win2k8 server
When a user logs out not all handles are freed (on logon it creates 3
handles , also a bit strange) and when the socket is closed only 2 of
them are freed resulting in a core that is notgoing to run long.
This bug existed before untill poy changed the way the socket was
closed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/837544/+subscriptions
References