The NtfLogger::coll_ is used to store the notification in order to serve the
NtfReader but the NtfLogger::coll_ has not removed all its elements so that the
destructor of NtfNotification to be invoked.
Valgrind has complained that these notifications have not been released if the
osafntfd has stopped. However, if the ntf service is stopped, the system will
reboot anyway.
So for now this is not a problem if NtfLogger::coll_ does not remove all
elements (probably in NtfLogger destructor)
---
** [tickets:#999] NTF: memory leak due to missing removal of std:tr1:shared_ptr
in last container**
**Status:** assigned
**Milestone:** 4.5.0
**Created:** Wed Aug 20, 2014 02:09 PM UTC by Minh Hon Chau
**Last Updated:** Fri Aug 22, 2014 12:22 AM UTC
**Owner:** Minh Hon Chau
In the method NtfAdmin::deleteConfirmedNotification(...), the NtfNotification
object should be destroyed after NtfAdmin::notificationMap erases the
NtfSmartPtr.
But the fact that there's another container (NtfLogger::coll_) still owning
this shared_ptr, thus the destructor of NtfNotification will not be invoked.
That causes memory leak because NtfLogger::coll_ has never removed its element
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
