http://forum.codejock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Mon, 08 Jun 2026 19:49:24 +0000 Tue, 18 Feb 2014 03:04:40 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 forum.codejock.com/RSS_post_feed.asp?TID=22209 http://forum.codejock.com/forum_images/codejock-logo.gif http://forum.codejock.com/ http://forum.codejock.com/forum_posts.asp?TID=22209&PID=72269&title=leak-reported-in-cxtpreportcolumns-class#72269 Author: rockstar
Subject: 22209
Posted: 18 February 2014 at 3:04am

In my application using XTP, there is a memory leak reported in the following function of XTP library source:

CXTPReportColumns::CXTPReportColumns(CXTPReportControl* pControl)
    : m_pControl(pControl)
{
    m_pGroupsOrder = new CXTPReportColumnOrder(this);
    m_pSortOrder = new CXTPReportColumnOrder(this);

    m_pTreeColumn = NULL;

}

I would like to know is it fine not deleting those variables, and can I ignore the leak report by VS 2008?
Is the InternalRelese() method called in the destructor alone is enough?:
CXTPReportColumns::~CXTPReportColumns()
{
    Clear();

    if (m_pGroupsOrder)
        m_pGroupsOrder->InternalRelease();
    if (m_pSortOrder)
        m_pSortOrder->InternalRelease();
}

Also leaks reported in following places:
CXTPReportRecordItemEditOptions::CXTPReportRecordItemEditOptions()
{
...
    m_pConstraints = new CXTPReportRecordItemConstraints();
...
}
void CXTPReportColumn::_initData(.....
{
...
    m_pEditOptions = new CXTPReportRecordItemEditOptions();
...
}

I am using the XTP version 15.0.2.

Thanks & Regards

]]> Tue, 18 Feb 2014 03:04:40 +0000 http://forum.codejock.com/forum_posts.asp?TID=22209&PID=72269&title=leak-reported-in-cxtpreportcolumns-class#72269