Memory leak in BufferedSocket

[Big Muscle]

This bug has been found in BufferedSocket::checkEvents();

When some function (for example threadConnect()) throws an exception, checkEvents will throw it to upper level (to BufferedSocket::run()) where it's handled. When this occurs, "p.second" in checkEvents() won't be deleted and will be lost, because it has already been removed from "tasks" before exception.

There are two possible solutions:
a) catch exception in checkEvents() where "p.second" will be deleted and then the exception will be thrown again.
b) make TaskData as "Smart Pointer" so it would delete itself when reference is lost.

[Jacek Sieka (arnetheduck)]

good bug report