Gareth,
I tried deleting memory manager and system crashes.
It happens only when I create two parser instances simultaneously using only
one MemoryManager pointer. System crashes when I delete both of the parsers
since parser is also trying to delete the memory manager in the following
code and already I have deleted the MemoryManager pointer. System works fine
if I do not delete the MemoryManager pointer myself.
template <class TElem> RefVectorOf<TElem>::~RefVectorOf()
{
if (this->fAdoptedElems)
{
for (unsigned int index = 0; index < this->fCurCount; index++)
delete this->fElemList[index];
}
fMemoryManager->deallocate(this->fElemList);//delete [] this->fElemList;
}
Below is the stack trace of the code
xercesc_2_3::RefVectorOf<xercesc_2_3::DOMNode>::~RefVectorOf<xercesc_2_3::DO
MNode>() line 139 + 21 bytes
xercesc_2_3::RefStackOf<xercesc_2_3::DOMNode>::~RefStackOf<xercesc_2_3::DOMN
ode>() line 108 + 8 bytes
xercesc_2_3::RefStackOf<xercesc_2_3::DOMNode>::`scalar deleting
destructor'(unsigned int 1) + 15 bytes
xercesc_2_3::RefArrayOf<xercesc_2_3::RefStackOf<xercesc_2_3::DOMNode>
>::deleteAllElements() line 259 + 37 bytes
xercesc_2_3::DOMDocumentImpl::~DOMDocumentImpl() line 220
xercesc_2_3::DOMDocumentImpl::`vector deleting destructor'(unsigned int 1) +
84 bytes
xercesc_2_3::DOMDocumentImpl::release() line 1324 + 30 bytes
xercesc_2_3::AbstractDOMParser::cleanUp() line 175
xercesc_2_3::AbstractDOMParser::~AbstractDOMParser() line 144
xercesc_2_3::DOMBuilderImpl::~DOMBuilderImpl() line 109 + 47 bytes
XmlTreeApplication::~XmlTreeApplication() line 39 + 55 bytes
XmlTreeApplication::`scalar deleting destructor'(unsigned int 1) + 37 bytes
xercesc_2_3::DOMBuilderImpl::release() line 422 + 30 bytes
XmlDocumentTree::~XmlDocumentTree() line 66 + 19 bytes
XmlDocumentTree::`scalar deleting destructor'(unsigned int 1) + 37 bytes
EsSgmlApplication::~EsSgmlApplication() line 78 + 35 bytes
Any suggestion?
Thanks & Regards
Vikas Agrawal
-----Original Message-----
From: Gareth Reakes [mailto:[EMAIL PROTECTED]
Sent: 07 October 2003 17:58
To: Agrawal, Vikas (ELS)
Cc: '[EMAIL PROTECTED]'
Subject: Re: Is it a typing mistake in XMLPlatformUtils::Initialize
Hi Vikas,
> void XMLPlatformUtils::Initialize(const char* const locale
> , const char* const nlsHome
> , PanicHandler* const panicHandler
> , MemoryManager* const
memoryManager)
> {
>
> if (gInitFlag == LONG_MAX)
> return;
>
> // Set pluggable memory manager
> if (!fgMemoryManager)
> {
> if (memoryManager)
> {
> fgMemoryManager = memoryManager;
> fgMemMgrAdopted = false; // Vikas: should it not be set to
true
We do not want to adopt this. The user who passed this in is still
responsible for it.
> else
> {
> fgMemoryManager = new MemoryManagerImpl(); // Vikas: and here
> fgMemMgrAdopted should not be set to false
Here we create one so we must be aware that we need to delete it. The
fgMemMgrAdded has already been set to true so we don't need to do anything
here.
Gareth
--
Gareth Reakes, Head of Product Development +44-1865-203192
DecisionSoft Limited http://www.decisionsoft.com
XML Development and Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]