Ah, tricky things to track :) The SID command won't cause problems with the SID command because the state isn't normal yet. What comes to INF, the state is just changed to normal before the info function is called (which also triggers updateCounts). I'm not sure about NMDC because I don't know it that well.
-- 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++: New 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
