Or possibly BufferedSocket should always have a child object that gets deleted when the shutdown function is handled... that would directly make it safe to use the async call for all sockets without taking care of the deletion.
-- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to DC++. https://bugs.launchpad.net/bugs/1194299 Title: Threading issues in hub management Status in DC++: Fix Committed Bug description: AdcHub::info is called from various different threads (timer, refresh, hub, GUI) but it's not thread safe. lastInfoMap is unprotected while it can be modified from different threads simultaneously. This has been fixed in AirDC++ by syncing the info calls from other threads to the hub thread. Client::updateCounts is another function that shouldn't be called from different threads because the hub counts may go wrong. This started to cause real problems in AirDC++ when the info calls from TimerManager were synced to the hub threads, which caused them to get executed asynchronously all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/dcplusplus/+bug/1194299/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
