From: Hans F. <han...@er...> - 2013-08-23 15:01:14
|
The change seems fine but I think I have found another memory leak. saImmOmFinalize() should finalize all not yet finalized handles. From IMM A.03 spec (did not have A.02 at hand): "If the saImmOmFinalize() function completes successfully, it releases all resources acquired when saImmOmInitialize_3() was called. Moreover, it implicitly invokes: * saImmOmSearchFinalize() on all search handles initialized with immHandle and not yet finalized. * saImmOmAccessorFinalize() on all accessor handles initialized with immHandle and not yet finalized. * saImmOmAdminOwnerFinalize() on all administrative owner handles initialized with immHandle and not yet finalized." That does not seem to happen when I run "valgrind immomtest" since it produces a number of complaints about accessorGet test cases. And these test cases does not do an explicit accessorFinalize(). Comments? Thanks, Hans From: Zoran Milinkovic [mailto:zmi...@us...] Sent: den 21 augusti 2013 14:29 To: [opensaf:tickets] Subject: [tickets] [opensaf:tickets] #549 IMM: saImmOmAccessorGet_2 does not free object name * status: unassigned --> review ________________________________ [tickets:#549]<http://sourceforge.net/p/opensaf/tickets/549/> IMM: saImmOmAccessorGet_2 does not free object name Status: review Created: Wed Aug 21, 2013 11:51 AM UTC by Zoran Milinkovic Last Updated: Wed Aug 21, 2013 11:51 AM UTC Owner: Zoran Milinkovic saImmOmAccessorGet_2 does not free a memory allocated for an object name which causes a memory leak. ________________________________ Sent from sourceforge.net because ope...@li...<mailto:ope...@li...> 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. |