id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc 95,Is the logging of Duplicate accurate about the MO pointer?,michelpons,michaelhalloran,"When analyzing logs obtained with COLTT 1.08.5 with two different PMEs and the same PMC (the CPP Mixer Splitter example), I have noticed that within the Calculate method, the Duplicate method is called twice (because there are two feeds to the UO) and each time the pointer returned appears as the same. This is worrying me because in fact the previous MO is not released before a new duplicate is done according to the following excerpt of the CPP Mixer Splitter code: bool Duplicate(Material &m,wstring &error) {ATLASSERT(materialObject); //class should be instanciated properly //create a new material object MaterialObjectWrapper *MO=materialObject->Duplicate(error); <------- NEW ONE IS OBTAINED if (!MO) return false ; //fail //clean up old MO in m if (m.materialObject) m.materialObject->Release(); <------- OLD ONE IS RELEASED //set new m.materialObject=MO; //ok return true ; } So while this has no consequence really for the CPP Mixer Splitter it is of interest to know if the pointer mentioned in the log is the real pointer or one pertaining to the CO logger. Could this be assessed?",defect,closed,critical,2.1,COLoggers,Development,fixed,DuplicateMOs,