 |
 |
 |
Hallo everyone
i am using the load function and each time a load a new file my memory
grows. I have trubble shouted this an dhav e no idea what to do.
when checking with Queryinterface:
HRESULT hRes = m_pDoc.CoCreateInstance( __uuidof( DOMDocument ));
if( FAILED( hRes ))
{
ATLTRACE( L"Failed to instantiate IXMLDOMDocument\n" );
}
HRESULT hr;
IUnknown *punk;
hr=m_pDoc->QueryInterface(IID_IUnknown, (void**)&punk);
int temp=punk->Release();
the temp integer shows that the interface has 2 references to the object. At
this point Iam only expected one reference.
after crating an instance of the object I use
hRes = m_pDoc->load( CCom Variant(varXmlSource), &isSuccessful );
the file loaded an parsed without any problem. The problem is that when i
wants to laod a new file. The memory exceeds, and this goes on and on for
each file.
I have tried to do m_pDoc.release before loading again, that shouldnt be
neccessary according to msnd help. But the memory still grows for each load.
I have start to wonder if i may have som old dll file but not sur of how a
can detect verson of my xml parser
i would be grateful for any help
Tony
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |