[
https://issues.apache.org/jira/browse/XERCESC-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lyublena Antova updated XERCESC-1938:
-------------------------------------
Attachment: patch
Patch with suggested fixes
> Memory allocation does not always go through the MemoryManager
> --------------------------------------------------------------
>
> Key: XERCESC-1938
> URL: https://issues.apache.org/jira/browse/XERCESC-1938
> Project: Xerces-C++
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 3.1.1
> Reporter: Lyublena Antova
> Attachments: patch
>
>
> When trying to use Xerces with the pluggable MemoryManager I discovered that
> on several occasions objects are instantiated with the global new operator
> that does not use the memory manager. Here are some of those cases:
> - initializing the EncodingValidator in EncodingValidator.cpp
> - creating a DOMImplementationListImpl in DOMImplementationImpl.cpp and
> DOMImplementationRegistry.cpp
> - creating a DOMNodeListImpl in DOMNodeImpl.cpp
> - creating a DOMDocumentTypeImpl in DOMImplementationImpl.cpp
> - creating a XMLCh array in XMLString.cpp
> ...
> In our code we essentially forbid the use of plain global "new" so the above
> cases blow up when Xerces is linked against our codebase.
>
> I will post a patch soon with the suggested fixes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
