Whenever you are developing sufficiently large complex programs in languages like C++ or Java you have to deal with memory issues. This holds true especially when your program is supposed to run 24/7 or close to that. Because these kinds of issues can be hard to get right Java has this nice little helper, the garbage collector. But as Java solves all memory problems, or maybe not? points out, you can still easily shoot yourself in foot or even blow your whole leg away. One of the problems stated there is that memory leaks can easily occur due to incorrect listener relations. Whenever a listener is not removed properly, which is either a large object itself or has references to such objects, it’s only a matter of time until your program dies with “OutOfMemoryError” as its last words. One of the proposed solutions is to use Java weak pointers for listener management. Let’s see how this translates to C++.
Observer/listener management in C++ is often done using pointers to listener objects. Pointers are pretty weak by default. They can be :
- null
- pointing to a valid object
- pointing to an invalid memory address
In listener relationships especially the latter can be a problem. For example, simple listener management could look like this:
class SimpleListenerManagement
{
public:
void addListener(MyListener* listener);
void removeListener(MyListener* listener);
void notifyListeners();
private:
std::list<MyListener*> listeners_;
};
void SimpleListenerManagement::notifyListeners()
{
// call notify on all listeners
for (std::list<MyListener*>::iterator iter = listeners_.begin();
iter != listeners_.end();
++iter)
{
(*iter)->notify(); // may be a bad idea!
}
}
In notifyListeners(), the pointer is used trusting that it still points to a valid object. But if it doesn’t, for instance because the object was deleted but the client forgot to removed it from the listener management, well, too bad.
Obviously, the situation would be much better if we didn’t use raw pointers but some kind of wrapper objects instead. A first improvement would be to use boost::shared_ptr in the listener management:
typedef boost::shared_ptr<MyListener> MyListenerPtr;
class SimpleListenerManagement
{
public:
void addListener(MyListenerPtr listener);
void removeListener(MyListenerPtr listener);
void notifyListeners();
private:
std::list<MyListenerPtr> listeners_;
};
Provided that the given MyListenerPtr instance was created correctly by the client we can be sure now that all listeners exist when we call notify() on them. Seems much better now. But wait! Using boost::shared_ptr, we now hold strong references in our listeners list and are therefore kind of in the same situation as described in the post mentioned above. If the client forgets to remove its MyListenerPtr instance it never gets deleted and may be in a invalid state next time notify() is called.
A solution that works well in most cases is to use boost::weak_ptr to hold the listeners. If you see boost::shared_ptr on a level with normal Java references, boost::weak_ptrs are roughly the same as Java’ s weak references. Our listener management class would then look like this:
typedef boost::shared_ptr<MyListener> MyListenerPtr;
typedef boost::weak_ptr<MyListener> MyListenerWeakPtr;
class SimpleListenerManagement
{
public:
void addListener(MyListenerPtr listener);
void removeListener(MyListenerPtr listener);
void notifyListeners();
private:
std::list<MyListenerWeakPtr> listeners_; // using weak_ptr
};
Note that addListener and removeListener still use MyListenerPtr as parameter. This ensures that the client provides valid listener objects. The interesting stuff happens in notifyListeners():
void SimpleListenerManagement::notifyListeners()
{
std::list<MyListenerWeakPtr>::iterator iter = listeners_.begin();
while(iter != listeners_.end())
{
if ((*iter).expired())
{
iter = listeners_.erase(iter);
}
else
{
MyListenerPtr listener = (*iter).lock(); // create a shared_ptr from the weak_ptr
listener->notify();
++iter;
}
}
}
Each weak_ptr can now be checked if its object still exists before using it. If the weak_ptr is expired, it can simply be removed from the listeners list. With this implementation the removeListener method becomes optional and can as well be omitted. The client only has to make sure that the shared_ptr holding the listener gets deleted somehow.
Schneide Blog 